solo-skill-audit
/skill-audit
Audit a skill against the quality checklist based on Anthropic's internal best practices for Claude Code skills. Reads the skill's SKILL.md, references/, scripts/, and evaluates across 12 dimensions.
Source: https://x.com/trq212/status/2033949937936085378
Checklist Reference
Full checklist with scoring rubric: references/checklist.md
Steps
-
Locate skill from
$ARGUMENTS:- If name: search
skills/{name}/SKILL.mdin current project, then~/.claude/plugins/**/skills/{name}/SKILL.md - If path: read directly
- If empty: list available skills via Glob
**/skills/*/SKILL.md, ask via AskUserQuestion
- If name: search
-
Read skill contents (parallel):
SKILL.md— main skill filereferences/*— all reference files (if dir exists)scripts/*— all scripts (if dir exists)assets/*— all assets (if dir exists)- Count total lines of SKILL.md
-
Read checklist from
references/checklist.md -
Evaluate each dimension — for every checklist item, assess based on what you read:
For each of the 12 dimensions:
- State what you found (evidence)
- Score 0, 1, or 2 (use rubric from checklist)
- If score < 2: give one specific fix
-
Determine category — classify skill into one of 9 types from checklist. Flag if it straddles multiple.
-
Output scorecard:
## Skill Audit: {skill-name} **Score:** {N}/24 (Grade: {A/B/C/D/F}) **Category:** {type} **SKILL.md:** {N} lines | **References:** {N} files | **Scripts:** {N} files | # | Dimension | Score | Notes | |---|-----------|-------|-------| | 1 | Category Fit | {0-2} | {one line} | | 2 | Description Quality | {0-2} | {one line} | | 3 | Progressive Disclosure | {0-2} | {one line} | | 4 | Gotchas | {0-2} | {one line} | | 5 | Don't State Obvious | {0-2} | {one line} | | 6 | Flexibility | {0-2} | {one line} | | 7 | Setup & Config | {0-2} | {one line} | | 8 | Memory & State | {0-2} | {one line} | | 9 | Scripts & Code | {0-2} | {one line} | | 10 | Allowed Tools | {0-2} | {one line} | | 11 | Argument Handling | {0-2} | {one line} | | 12 | Output & Artifacts | {0-2} | {one line} | ### Top 3 Fixes (highest impact) 1. {fix} 2. {fix} 3. {fix} -
Batch mode — if
$ARGUMENTSis "all" or "*":- Find all skills via Glob
- Run audit on each
- Output summary table sorted by score (worst first)
- Identify common weaknesses across the set
Gotchas
- N/A dimensions still score 2 — if a skill genuinely doesn't need config/state/scripts, don't penalize it. Score N/A as 2. Only score 0-1 when the skill SHOULD have it but doesn't.
- Gotchas ≠ Common Issues — "Common Issues" is troubleshooting (reactive). Gotchas are preventive — things Claude would get WRONG by default. A skill with only "Common Issues" scores 1, not 2.
- Line count is a smell, not a rule — 500-line SKILL.md with no references is suspicious. But 400 lines of dense, non-obvious content is fine. Check if content COULD be extracted, not just if it's long.
- Description under 300 chars — long descriptions dilute the trigger signal. Claude scans ALL skill descriptions at session start. Shorter = sharper matching.
Common Issues
Can't find skill
Cause: Skill not in expected path or using different directory structure. Fix: Use full path to SKILL.md as argument. Or run with "all" to discover available skills.
Score seems unfair
Cause: Some dimensions don't apply to the skill type. Fix: N/A dimensions score 2. Re-read the rubric — it accounts for genuinely stateless or config-free skills.
More from fortunto2/solo-factory
solo-research
Use when "research this idea", "find competitors", "check the market", "domain availability", "market size", "analyze opportunity", or need evidence before validation. Do NOT use for idea scoring (/validate) or SEO auditing (/seo-audit).
42solo-swarm
Use when "swarm research", "parallel research", "investigate fast", "3 agents", "team research", or want faster multi-angle alternative to /research. Do NOT use for solo research (/research) or idea scoring (/validate).
33solo-build
Use when "build it", "start building", "execute plan", "implement tasks", "ship it", track ID referenced, or plan tasks need execution. Do NOT use for planning (/plan) or scaffolding (/scaffold).
32solo-humanize
Use when "humanize this", "make it sound human", "strip AI patterns", "clean up the copy", or text reads like AI-generated output with em dashes and stock phrases.
32solo-audit
Use when "audit KB", "check frontmatter", "find broken links", "tag cleanup", "knowledge base quality", or docs need health check. Do NOT use for SEO audits (/seo-audit) or code reviews (/review).
30solo-scaffold
Use when "scaffold project", "create new project", "start new app", "bootstrap project", "set up from PRD", or need project from PRD + stack template. Do NOT use for planning features (/plan) or PRD generation (/validate).
29