name	description
create-skill	Recognizes when a recurring mistake or workflow could be captured as a skill. Suggests creating skills proactively.

When to Suggest Creating a Skill

Recognize These Patterns

Suggest creating a skill when:

1. Repeated corrections - User corrects the same type of mistake more than once
2. Domain-specific workflow - A task requires checking external sources first (like viem/chains)
3. Project conventions - User explains how things should be done in their codebase
4. Tool-specific knowledge - Library has patterns that aren't in training data
5. "You always get this wrong" - User expresses frustration about recurring errors

How to Suggest

When you notice a pattern, say something like:

"This seems like something we could capture in a skill so I don't make this mistake again. Want me to create one?"

Skill Basics (for when user says yes)

• Location: ~/.claude/skills/<name>/SKILL.md (global) or .claude/skills/<name>/SKILL.md (project)
• Format: YAML frontmatter with name and description, then markdown instructions
• Key: Be specific about what to do, include the "why", add examples

Examples of Good Skill Candidates

• "Always check X source before doing Y"
• "In this codebase, we use pattern A not pattern B"
• "When working with library Z, first verify W"
• "Never use X approach, always use Y instead"