Skill audit

Skill magnusrodseth/dotfiles/.claude/skills/skill-audit

Audit installed Claude Code skills for context-budget cost and real usage. Inventories ~/.claude/skills, estimates the always-loaded token cost of each description, and mines ~/.claude/projects transcripts for actual invocations to find unused skills. Use when the user asks to "audit skills", "clean up skills", "find unused skills", "skill budget", "too many skills", or wonders what their skills cost in context.From its SKILL.md

Install

npx -y skills add magnusrodseth/dotfiles --skill skill-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
2 stars2 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.

SKILL.md

2.5 KB, 523 tokens by cl100k_base, as published. Nobody here has run it

Skill Audit

Every installed skill's name + description is loaded into context in every session. This skill finds which ones earn that cost.

Workflow

Run the analyzer:

bash ~/dotfiles/.claude/skills/skill-audit/scripts/skill-audit.sh

Add a project's skills to the inventory with --root (repeatable):

bash ~/dotfiles/.claude/skills/skill-audit/scripts/skill-audit.sh \
  --root ~/dev/personal/vault/.claude/skills

Read the report:

Header: total skills and the always-loaded token cost per session.
Main table: used skills, most-used first, with last-used date and source.
UNUSED IN WINDOW: removal candidates, most expensive first.

Suggest removals; delete only when the user confirms. Removal mechanics depend on the SOURCE column:

Source	Managed by	Remove with
`skills-cli`	skills.sh lock file	`npx skills remove <name>`, then `bash ~/dotfiles/scripts/skills/packages.sh export` and commit the lock file
`dotfiles`	authored in dotfiles	delete `~/dotfiles/.claude/skills/<name>/`, run `bash ~/dotfiles/scripts/skills/link-dotfiles-skills.sh` (prunes the global link), remove a leftover `~/.agents/skills/<name>` symlink if present, commit
`local`	nothing (untracked real dir in `~/.claude/skills`)	delete the dir; or move keepers into `~/dotfiles/.claude/skills/` so they become tracked and validated

Caveats

Usage evidence is heuristic: Skill tool calls, slash commands, and SKILL.md reads found in transcripts. A skill invoked another way (or on another machine) can look unused.
The window is bounded by transcript retention; the report prints the oldest transcript date. Roughly a month of history is typical.
Zero uses is not automatically removable: reference skills (e.g. runtime contracts another skill depends on) and rarely-needed safety skills can be worth their tokens. Judge, don't just delete.
Plugin skills are not scanned; manage those via /plugin.
Cross-machine: skills used only on the other machine look unused here. Check before removing lock-file entries that sync via dotfiles.

What ships with it: 1 file

5.5 KB alongside SKILL.md, 1 of them executable

scripts/

skill-audit.shruns5.5 KB