Skill graveyard
Audit which Claude Code skills you actually use — surface dead installs and hallucinated invocations from your session logs.
npx -y skills add sfrangulov/skill-graveyard --skill skill-graveyardAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Audit which Claude Code skills you actually invoke. Use when the user wants to find dead/unused skills, hallucinated skill invocations, per-project skill stats, or token cost of installed skill metadata. Triggers on "what skills don't I use?", "clean up my skills", "why didn't this skill work?", "audit skills". Runs locally; reads ~/.claude session JSONL logs. No network calls.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, as published. Nobody here has run it
skill-graveyard
CLI that audits Claude Code skill usage. Two signals from one parser:
- Dead installs — installed but never invoked → safe to remove.
- Hallucinated invocations — invoked but not installed → typos, external-framework registrations, or model tool/skill confusion.
How to invoke
Run via npx skill-graveyard@latest <subcommand> [flags] — no install needed.
Subcommands
audit(default) — classify into active / dead / missing / hallucinated. Flags:--days N,--only <bucket>,--json,--claude-dir <path>.prune— print removal commands for dead skills.--applyto execute (user/agents only; plugin removals always print only).suggest— triage hallucinated/missing into actionable buckets.projects— per-project usage breakdown (cwd from sessions).cost— token cost estimate of installed metadata vs invocations.outdated— check installed plugins / git skills for upstream updates (network).
Decision flow
- "are there skills I don't use?" →
npx skill-graveyard@latest - "clean up unused skills" →
prune, thenprune --apply - "skill X didn't work" →
suggest(look for hallucinated/missing entry) - per-project view →
projects - token cost →
cost - check updates →
outdated
After running, print binary output as-is. Do not summarize unless the user asks.