glitchwerks

Audits a project's effective Claude Code configuration — custom and plugin-provided agents and skills — and produces a structured overlap/conflict report with keep / modify / drop recommendations scoped to the project's stated objectives. Trigger this skill whenever the user types /claude-audit, asks to "audit my claude config", "find overlap in my agents", "check for skill conflicts", "are any of"

Sets up claude-prospector's plugin-owned Python virtual environment. It's invoked by /setup-prospector or phrases like "set up claude-prospector" and "fix prospector", but not for "dashboard" or "skill adoption".

Use this skill when the user explicitly asks to regenerate, rebuild, or refresh the `claude-prospector` token-usage dashboard. It runs `python -m claude_prospector dashboard`, writes the HTML file, and reports the output path.

Use when the user asks an interpretive question about their Claude Code token spend — what's interesting, what's anomalous, what to change. This skill produces insights and questions; it does NOT enumerate top consumers (the dashboard does that).