skill-auditlisted

# Skill Audit Skills drift. Each edit is made with one file open, so over time two files of the same skill come to disagree, a rule ends up in a file nothing tells Claude to read, and a pointer names a path or skill that was since renamed. A per-file review cannot see any of these. This skill reads the whole skill at once, as one system. The audit has two passes, run by two readers who never share a context: 1. **Read.** A subagent with a fresh context reads the skill and writes a report. It fixes nothing. 2. **Fix.** This session re-verifies every finding against the files, then fixes what is clear and asks about what is not. A finding is a lead until the fix pass confirms it. A reader who fixes its own findings tends to trust them; a second reader who must re-check each one catches the false positives. ## Arguments - `<skill>`: the skill's folder name. Look first for `.claude/skills/<skill>/SKILL.md` in the current project, then `~/.claude/skills/<skill>/SKILL.md`. If neither exists, list the skills you can see and stop. Skills installed from a plugin are out of scope: their updates would overwrite any fix, so send findings to the plugin's author. - `report`: run the read pass only. - `fix`: run the fix pass only, on the newest open report for `<skill>`. - No second word: run the read pass, then the fix pass if the report has findings. **Report location:** `.claude/skill-audits/<skill>-<YYYY-MM-DD>.md` beside the `skills/` folder the skill lives in (the project's `.c