skill-maker

Write the description in third person with both what the skill does and when to use it, embedding trigger words like technical terms and common user phrasings. Keep it between 1 and 1024 characters and avoid vague statements like "helps with coding."

One skill equals one directory with a SKILL.md file at its root, where the frontmatter name exactly matches the directory name in lowercase kebab-case. Put executable scripts in scripts/, examples in examples/, and long reference material in reference/.

Skip creating a skill for one-off conversations, project-specific conventions that belong in AGENTS.md, or tasks fully enforceable by mechanical validators or lint rules. Skills are for reusable judgment, team conventions, and domain procedures.

Keep SKILL.md short and scannable since it loads into context on activation. Move long manuals and detailed references into adjacent reference/ or examples/ files, linking them only one level deep from SKILL.md.

The name must match the directory exactly and follow the pattern of lowercase letters, digits, and single hyphens, with no leading or trailing hyphens and no double hyphens. Choose searchable names like pdf-form-fill instead of generic ones like helper or utils.