Menu
Create a new reusable skill from scratch. Triggers on "create a skill", "new skill", "make a skill called", "add a skill for", "/skill-creator".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | skill-creator |
| description | Create a new reusable skill from scratch. Triggers on "create a skill", "new skill", "make a skill called", "add a skill for", "/skill-creator". |
| allowed-tools | Read, Write, Edit, Glob, Grep |
Trigger: /skill-creator or "create a skill" or "make a skill called" or "add a skill for"
Description: Builds a new SKILL.md from scratch by gathering requirements, writing the step-by-step instructions, creating the file, and wiring it into the workflow map.
Gather requirements — ask the user (if not already clear):
fix-bug, new-endpoint)Check for duplicates — glob existing skills for similar names or trigger phrases:
Glob pattern="**\SKILL.md" path=".claude\skills"
Read any close matches. If a duplicate exists, report it and ask: "Update existing or create new?"
Draft the SKILL.md using this template:
---
name: skill-name
description: One-line description — used for skill discovery. Include trigger phrases.
allowed-tools: Read, Edit, Write, Glob, Grep
---
# Skill: skill-name
**Trigger:** `/skill-name` or "trigger phrase A" or "trigger phrase B"
**Description:** What this skill does in one sentence.
**Allowed Tools:** Read, Edit, Write, ...
---
## Steps
1. **Step one** — what to do first
2. **Step two** — next action
3. ...
---
## Notes
- Any caveats, edge cases, or project-specific rules
Show the draft to the user and ask: "Does this look right, or any changes before I write it?"
Write the file once approved:
.claude/skills/<skill-name>/SKILL.mdAdd to CLAUDE.md skill map if it belongs in a workflow — find the relevant row and insert it.
Report: "Skill /<skill-name> created at .claude/skills/<skill-name>/SKILL.md. Trigger: [phrases]. Added to workflow: [yes/no]."
allowed-tools in frontmatter controls what the skill can use — be conservative; only list tools the steps actually needScans a real codebase and writes coding-conventions.md from what it actually finds — variable style, SQL patterns, error handling, INSERT strategy, naming. Run once on any new project to bootstrap the convention system. Triggers on "scan conventions", "generate conventions", "bootstrap conventions", "extract conventions from code", "what are the conventions".
Security audit — checks auth, SQL injection, exposed endpoints, and sensitive data. Triggers on "security check", "is this secure", "check for vulnerabilities", "check auth", "audit security", "security audit".
Use when switching environments, updating config values, or verifying URLs/settings. Triggers on "check environment", "switch to production", "update URLs", "check config", "is this prod-ready".
Use when verifying a feature works, after making changes, or before shipping. Triggers on "verify this works", "test this", "does this work", "run the checklist", "before I ship", "check this end to end".
Use when cleaning up, simplifying, or restructuring existing code without changing behavior. Triggers on "refactor", "clean up", "simplify this", "this is getting messy", "too long", "hard to read", "extract this".
Use when the user wants to review a file for bugs, antipatterns, or quality issues. Triggers on "review", "check for issues", "look for problems", "audit", "before I ship".