aie-skill-creatorlisted

# Skill Creator One job: turn a task or workflow into a skill a stranger can install and Claude will actually load at the right moment. A good skill is discoverable (triggers when it should), tight (loads little until needed), and safe. Read `reference/skill-anatomy.md` before writing, `reference/quality-rubric.md` before finishing, and `reference/packaging.md` when shipping. ## The loop: Scope → Draft → Reference → Test → Package ### 1. Scope — one skill, one job Pin down, from the person or by inference: - **The job** in one sentence. If it's really three jobs, that's three skills — say so. - **Triggers** — the exact words and situations where it should fire ("de-slop this," "audit my SEO"). List 5–10. - **Inputs / outputs** — what it's handed, what it returns. - **Safety** — does it write files, send messages, call external services, run code? Note what needs approval. Don't start writing until the job is one sentence. ### 2. Draft the frontmatter, then the SKILL.md Frontmatter is two keys only: `name` (lowercase-hyphenated, matches the folder) and `description`. **The description is the whole ballgame for triggering** — Claude reads only name+description to decide whether to load the skill. Write it concrete and keyword-rich, say what it does *and when to use it*, and end with the trigger phrases. See the good/bad examples in `reference/skill-anatomy.md`. Then write the body: - Lead with the one-sentence job. - Give a short, numbered procedure or a named loop. Steps