Track skill usage and identify dead code
claude-skill-trackerskillsetup L1★0
kevinwang04/claude-skill-tracker ↗What it does
Track Claude Code skill usage and identify stale skills
Best for
Quarterly skill inventory and cleanup when you have 20+ skills and can't remember which ones are actually used.
Inputs
- · [object Object]
- · [object Object]
Outputs
- · [object Object]
- · [object Object]
Requires
- · Claude Code PostToolUse hook
- · ~/.claude/settings.json (hook registration)
- · Node.js built-in modules only (zero npm dependencies)
Preconditions
- · claude-skill-tracker installed globally or project-local
- · init run to register PostToolUse hook in settings.json
- · Ollama/Claude Code running normally (hook fires on every Skill call)
Failure modes
- · Hook not triggered if Claude Code version incompatible
- · JSONL log grows unbounded (no rotation built in)
- · Stale skill threshold (14 days) may not match user's retention policy
- · No data if no skills invoked since init
Trust signals
- · Zero npm dependencies (100% Node.js stdlib)
- · JSONL local-only storage (no cloud/telemetry)
- · ANSI color + Unicode tables for terminal UX
- · Status icons: ● active, ◐ stale, ○ zombie, · unused