write-a-skill

Start with YAML frontmatter containing a name and description, then add a Markdown body with a quick start, workflows, and advanced features. Keep the file under 100 lines and split longer content into separate reference files.

A good description states what the skill does in the first sentence and when to trigger it in the second, using specific keywords and contexts. Keep it under 1024 characters, write in third person, and avoid vague phrases like "helps with documents."

Add utility scripts when operations are deterministic, such as validation or formatting, when the same code would be generated repeatedly, or when errors need explicit handling. Scripts save tokens and improve reliability over generated code.

Split content when SKILL.md exceeds 100 lines, when the content covers distinct domains, or when advanced features are rarely needed. Move detailed documentation into files like REFERENCE.md and link them from the main file.

Verify the description includes trigger phrases, SKILL.md stays under 100 lines, there is no time-sensitive information, terminology is consistent, concrete examples are included, and references go only one level deep.