| name | skill-creator-guide |
| description | Interactive guide for creating new Claude Code skills from scratch. Use when building a new skill, creating a SKILL.md, designing skill structure, or when the user says "create a skill", "build a skill", "make a new skill", or "help me write a skill". |
Skill Creator Guide
This is an interactive, step-by-step workflow for building a complete Claude Code skill.
Follow each phase in order. Do not skip steps.
Phase 1: Define the Use Case
Before writing anything, clarify exactly what the skill should do.
Ask the user (if not already specified):
- What task does this skill accomplish? (e.g., "generate API documentation", "review PRs", "deploy to staging")
- Who invokes it? User-only (
disable-model-invocation: true), Claude-only (user-invocable: false), or both (default)?
- What tools does it need? Built-in (Read, Write, Bash, Grep, Glob), MCP tools, or none?
- Where should it live? Personal (
~/.claude/skills/), project (.claude/skills/), or plugin?
Write down 2-3 concrete use cases in this format:
Use Case: [Name]
Trigger: User says "[example phrase]"
Steps:
1. [First action]
2. [Second action]
3. [Third action]
Result: [What the user gets]
Phase 2: Choose Skill Type
Determine which category fits best:
Reference content — Knowledge Claude applies to current work. Conventions, patterns, style guides.
- Runs inline (no
context: fork)
- No
disable-model-invocation
- Example: API conventions, coding standards, domain knowledge
Task content — Step-by-step instructions for a specific action.
