skill-audit

# Skill Audit Auditing the skill catalog itself. As the install grows from 5 skills to 50, the catalog goes from "I remember every skill" to "I have no idea what's in here." This skill makes the catalog legible to its owner. ## When to use - Once a quarter — hygiene pass - When Caddy starts surfacing the wrong skill repeatedly (signals a trigger-pattern mismatch) - When a new feature feels like it should be a skill but you can't remember if you already built one - After importing a skill bundle from another principal (e.g., from a public aigent-OS release) - When considering retiring a project area and want to know which skills go with it ## What it produces A markdown report with four sections: ### Section 1 — All skills, sorted by last invocation ``` | Skill | Last used | Total invocations (90d) | Description | |---|---|---|---| | /open | today | 47 | Start session, load vault context | | /close | today | 47 | End session, commit memory | | /caddy-enroll | 5 days ago | 12 | Add a skill to Caddy index | | /skill-name | 23 days ago | 3 | Example skill entry | | /old-experiment | 89 days ago | 1 | DEAD — flagged for retirement | ``` ### Section 2 — Dead skills (last used >60 days, <3 total invocations) These are candidates for retirement. List with: - Skill name + path - Last-used date - Total invocations - Recommendation: keep / archive / delete ### Section 3 — Caddy mismatch detection For each skill, compare the trigger keywords in `.claude/skill-index.json` again...