skill-auditlisted

# Skill Audit A skill library degrades the same way a prompt library does: things pile up, two skills quietly do the same job, and descriptions get vague enough that nothing triggers reliably. This skill audits the collection and produces a ruthless, actionable cleanup plan. ## Step 1 — Get the inventory Work from the best available source, in this order: 1. The skills visible in the current environment (if you can see an installed skills list, use it). 2. Otherwise, ask the user to paste their list from **Settings → Capabilities → Skills** — names are enough to start; descriptions make the audit much better. 3. If the user can share the actual SKILL.md files, audit those — that enables the deepest checks. Never invent skills the user didn't confirm having. ## Step 2 — Map each skill to its job For every skill, write one line: **the job it's hired for**, in the form "when [situation], produce [output]". If you cannot write that line from the skill's name and description, that is itself a finding — the skill has a triggering problem. ## Step 3 — Run the five checks 1. **Overlap.** Two or more skills hired for the same job (e.g. a /humanizer and an /anti-ai that both strip AI tells). Overlapping skills split triggering unpredictably — Claude may pick either one. Verdict: merge into one, or sharpen each description until the boundary is unambiguous (e.g. one runs on drafts, the other runs during prompt-writing). 2. **Vague triggers.** Descriptions like "helps with produc