create-skill

Create a directory containing a SKILL.md file with YAML frontmatter defining a name and description, followed by markdown instructions. Follow the four-phase workflow: discovery, design, implementation, and verification against the quality checklist.

SKILL.md requires YAML frontmatter with a name (max 64 chars, lowercase with hyphens) and a description (max 1024 chars), plus a markdown body with step-by-step instructions. Keep the body under 500 lines and move detailed content to reference files.

Write in third person, include both what the skill does and when to use it, and add specific trigger terms. For example, state the file formats or tasks handled and the phrases users might say when they need it.

Include scripts for fragile or repetitive operations where consistency matters, such as validation or form analysis. Scripts save tokens, avoid code generation errors, and should document required packages with explicit error handling.

Common anti-patterns include Windows-style paths, offering too many tool options without a default, time-sensitive instructions, inconsistent terminology, and vague names like helper or utils. Use one clear default approach and consistent terms throughout.