This skill should be used for periodic review of all Claude Code skills. Triggers include "audit my skills", "which skills need work", "skill inventory", or when starting a skill improvement session. Identifies staleness, gaps, redundancy, and prioritizes improvements.
/plugin marketplace add lnittman/skills/plugin install lnittman-lnittman-skills@lnittman/skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/audit-checklist.mdsystematic inventory and health check of all Claude Code skills. surfaces stale skills, identifies gaps in coverage, finds redundancies, and prioritizes improvement work.
"you can't improve what you don't measure"
| principle | application |
|---|---|
| evidence-based | check file dates, not memory |
| comprehensive | audit ALL skills, not just suspicious ones |
| actionable output | produce prioritized list, not just observations |
| periodic | run monthly or after major changes |
| use | skip |
|---|---|
| starting skill improvement session | mid-improvement on specific skill |
| monthly maintenance | just finished audit recently |
| "which skills need work" | know exactly which skill to improve |
| noticing skill quality variance | single skill question |
# list all skills with modification dates
for skill_dir in ~/.claude/skills/*/; do
skill_name=$(basename "$skill_dir")
mod_date=$(stat -f "%Sm" -t "%Y-%m-%d" "$skill_dir/SKILL.md" 2>/dev/null || echo "missing")
ref_count=$(ls "$skill_dir/references/" 2>/dev/null | wc -l | tr -d ' ')
echo "$mod_date | $skill_name | refs: $ref_count"
done | sort
for each skill, run consult-light:
cat <<'EOF' | cursor-agent -p --model gemini-3-pro
Quick skill depth check.
Skill: [skill_name]
SKILL.md preview: [first 50 lines]
Score 1-10 on:
1. Has decision tree?
2. Has concrete values?
3. Has anti-patterns?
4. References substantive?
Output JSON: {name, depth_score, issues: [], priority: high|medium|low}
EOF
group skills by health:
| category | criteria | action |
|---|---|---|
| healthy | depth >= 8, updated < 30 days | periodic review |
| stale | updated > 90 days | check if still relevant |
| shallow | depth < 6 | prioritize for skill-improve |
| orphaned | no references, minimal content | consider deletion |
| redundant | overlaps with another skill | consider merging |
map skills to your workflow:
Daily work involves:
├── Linear issues → issue-context skill? ✓
├── Code review → pr-audit skill? ✓
├── Testing → tdd-convex skill? ✓
├── Slack comms → slack skill? ✓
├── [your activity] → [skill]? ?
identify missing skills for frequent activities.
look for:
consolidation candidates:
create prioritized list:
## skill audit results - [date]
### immediate (depth < 5, high use)
1. [skill_name] - [issue] - [action]
### soon (depth 5-7, medium use)
1. [skill_name] - [issue] - [action]
### backlog (depth < 7, low use)
1. [skill_name] - [issue] - [action]
### healthy (depth >= 8)
1. [skill_name] - next review: [date]
### consider deletion
1. [skill_name] - reason: [orphaned/redundant/obsolete]
for each skill needing work:
| skill | current depth | target depth | blocker | effort |
|-------|---------------|--------------|---------|--------|
| name | 4/10 | 8/10 | needs source research | high |
# Skill Audit Report
**Date:** YYYY-MM-DD
**Total skills:** N
**Categories:** healthy: X, stale: Y, shallow: Z
## Health Summary
| skill | depth | last updated | refs | status |
|-------|-------|--------------|------|--------|
| loop | 8/10 | 2025-12-16 | 6 | healthy |
| tdd-convex | 5/10 | 2025-12-01 | 0 | shallow |
## Coverage Gaps
- [ ] No skill for: [activity]
- [ ] Weak coverage for: [domain]
## Redundancies
- skill-a overlaps with skill-b (recommend: merge)
## Prioritized Improvements
1. **[skill]** - [issue] - effort: [high/medium/low]
## Next Audit
Scheduled: YYYY-MM-DD
add to calendar or cron:
# first of month
skill-audit → slack dm luke "Monthly skill audit ready"
after using skill-improve:
skill-audit --skill=[improved_skill] --verify
| pattern | problem | fix |
|---|---|---|
| audit from memory | miss stale skills | check file dates |
| skip healthy skills | miss regression | include all in audit |
| audit without action | waste of time | produce prioritized list |
| one-time audit | skills decay | schedule periodic audits |
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.