| name | description |
|---|---|
create-skill |
Create and validate skills. USE WHEN user asks to create a new skill, validate skill structure, or canonicalize an existing skill. See skill-system.md for full spec. |
Create and validate skills following the canonical skill structure.
skills/
└── skill-name/ # kebab-case
├── SKILL.md # Required - main skill definition
├── Workflows/ # Optional - only if skill has sub-workflows
│ └── workflow.md
└── tools/ # Optional - scripts invoked by the skill
└── tool.ts # TypeScript (run with bun), Python, etc.
---
name: skill-name
description: What it does. USE WHEN [trigger phrases]. Key capabilities.
allowed-tools: # Optional - restrict tool access
- Read(path/**)
- Bash
---
# Skill Title
Brief description of what this skill does.
## Workflow Routing # ONLY if Workflows/ directory exists
| Trigger | Workflow |
|---------|----------|
| "do X" | [[Workflows/x.md]] |
## Examples
**Example 1: Description**
User: "example prompt"
→ Expected action/output
## Notes
Additional context, prerequisites, tips.- name: kebab-case, matches folder name
- description: Single line with
USE WHENclause - this is what Claude uses for skill routing - Workflow Routing: Only include if
Workflows/*.mdfiles exist - Examples: 2-3 concrete examples showing trigger → action
- Folder name is kebab-case
- SKILL.md has valid YAML frontmatter
-
descriptionincludesUSE WHENclause - Examples section with 2-3 patterns
- Workflow Routing only present if Workflows/ exists
- No orphan workflow files (all must be routed)
Example 1: Create a new skill
User: "create a skill for managing git worktrees"
→ Create skills/git-worktree/SKILL.md with proper structure
Example 2: Validate existing skill
User: "check if my summarize skill is structured correctly" → Read skill, validate against checklist, report issues
Example 3: Canonicalize a skill
User: "my skill works but might not follow best practices" → Review structure, suggest/apply fixes to match canonical format