skill-stocktake

name	skill-stocktake
description	Quality audit of installed skills with portfolio health dashboard
version	0.1.0
level	3
triggers	["/skill-stocktake","audit skills","skill health check","review skill quality"]
context_files	["context/project.md","context/learnings.md"]
steps	[{"name":"Mode Selection","description":"Choose Quick Scan (changed skills only) or Full Stocktake (all skills)"},{"name":"Skill Collection","description":"Gather all installed skills from .claude/skills/ directories"},{"name":"Evaluation","description":"Assess each skill against four dimensions using subagent"},{"name":"Verdict Assignment","description":"Assign one of four verdicts (Keep, Improve, Update, Retire, Merge)"},{"name":"Report Generation","description":"Generate portfolio health dashboard with findings"},{"name":"Cache Results","description":"Write results to ~/.claude/skills/skill-stocktake/results.json"}]

Skill Stocktake Skill

Quality audit of your installed skills. Identifies skills that are outdated, redundant, or underperforming.

What Claude Gets Wrong Without This Skill

Without systematic skill audits, Claude:

1. Continues using outdated skills that conflict with current best practices
2. Fails to identify redundant skills that bloat context windows
3. Doesn't detect skills with poor actionability (vague or unverifiable)
4. Misses opportunities to merge overlapping skills into stronger unified versions
5. Accumulates technical debt in the skill portfolio over time

The skill stocktake ensures your skill collection stays lean, current, and effective.

Two Modes

Quick Scan

Duration: 5-10 minutes Scope: Only skills modified in the last 30 days or flagged in learnings.md Use When: Regular maintenance, after adding new skills, post-session cleanup

Process:

1. Scan git history for modified SKILL.md files in last 30 days
2. Check context/learnings.md for skill-related issues (failures, confusion, conflicts)
3. Evaluate only the changed skills
4. Report verdicts and recommended actions

Full Stocktake

Duration: 20-30 minutes Scope: All skills in .claude/skills/core/ and .claude/skills/workflow/ Use When: Quarterly reviews, major version upgrades, before skill evolution

Process:

1. Enumerate all installed skills (core + workflow + learned)
2. Spawn a subagent with read-only access to evaluate each skill
3. Generate comprehensive portfolio health report
4. Identify clusters of related skills that could merge
5. Cache results for Quick Scan reference

Four Verdicts

KEEP: Skill is current, actionable, unique, and effective. No changes needed.

IMPROVE: Skill has value but needs refinement. Issues might include:

• Vague or unverifiable checklist items
• Missing anti-patterns section
• Unclear triggers
• No integration with context files

UPDATE: Skill content is outdated. Triggers might include:

• References deprecated tools or APIs
• Conflicts with newer skills
• Uses old architectural patterns
• Doesn't follow current SKILL.md format standards