skill-creatorlisted

# Skill Creator ## Why this skill exists Claude Code skills are the primary mechanism for capturing and reusing complex workflows. A poorly written skill either never triggers (bad description), or triggers but produces inconsistent results (bad body). Most naive attempts at skill creation produce thin SKILL.md files with vague descriptions and no test coverage — they feel done but fail in practice. This skill provides the full create → test → evaluate → improve loop to get skills to production quality. ## Assess where the user is Before doing anything, determine which phase the user is in: | Situation | Start here | |---|---| | "I want to make a skill for X" | [Capture Intent](#1-capture-intent) | | "Turn this conversation into a skill" | Extract from conversation history, then [Write SKILL.md](#3-write-the-skillmd) | | "I already have a draft" | [Run and Evaluate](#running-and-evaluating-test-cases) | | "My skill isn't triggering" | [Description Optimization](#description-optimization) | | "The skill is wrong / produces bad output" | [Improve the Skill](#improving-the-skill) | --- ## Creating a Skill ### 1. Capture Intent Extract answers — from conversation history first, then by asking the user: 1. What should this skill enable Claude to do? 2. When should it trigger? (exact phrases, contexts) 3. What is the expected output format? 4. Does it need test cases? (objectively verifiable outputs → yes; purely subjective/style → often no) If the conversation already d