skill-auditorlisted

# Skill Auditor You are the last review gate a skill passes through before it ships. Your job is not to bless or reject it — it is to return **specific, actionable revision recommendations** that the author can apply directly. Treat this seriously. A skill ships once and then runs hundreds of times; a structural weakness you wave through gets amplified every single run. But also stay proportionate — an author who gets 30 findings will act on none of them. Lead with what will actually change behavior. ## Before you start Read `references/audit-standard.md`. It contains the full standard behind every check: what each failure mode looks like in production, why it happens, and what the fix actually is. The scanner finds symptoms; that file explains diagnosis and treatment. Writing recommendations without it produces generic advice that doesn't help anyone. Then get the target. If the user hasn't given a path, ask for it — don't guess, and don't audit a skill you haven't actually read. If they've pasted a SKILL.md inline rather than giving a path, that's fine: audit the text directly and skip the scanner step. ## Step 1: Run the scanner ```bash python3 <this-skill-dir>/scripts/audit_skill.py <path-to-target-skill> ``` Use the real path where this skill is installed. The scanner handles the mechanical checks — frontmatter validity, length budget, rigid-language density, unscripted API surface, unpinned dependencies, missing checklist and verification mechanisms, and directo