Create an Agent Skill

Guide the creation of a new SKILL.md file that meets quality standards for agent skills.

Rules

1. One skill, one job. A skill should target exactly one workflow or domain. If you need the word "and" to describe what it does, split it into two skills.

2. Prefer gerund form for names. Per Anthropic's official guidance, use verb+ing: processing-pdfs, analyzing-spreadsheets, writing-documentation. Acceptable alternatives: noun phrases (pdf-processing) or action-oriented (process-pdfs). Avoid vague names (utils, helpers, tools) and overly generic ones (documents, data). Hard constraints from the spec: lowercase + numbers + hyphens only, max 64 chars, must not contain the reserved words anthropic or claude.

3. Write a trigger-oriented description in third person. The description field determines when the agent activates the skill. Start with "Use when..." and be specific enough to avoid false triggers but broad enough to catch the right moments. Always third person — Anthropic warns that I can… or You can use this… phrasing degrades discovery. Max 1024 chars.

   • Bad: "Helps with diagrams." / "I can fix your ASCII art."
   • Good: "Use when creating or fixing ASCII box diagrams, tables, or monospace text art to ensure proper alignment."