Audit a project's effective Claude Code configuration — custom and plugin-provided agents and skills — and produce 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 my agents duplicates", "what's redundant in my setup", or any similar request to review the agent/skill surface for the current project. Also trigger after a fresh plugin install when the user wants to verify nothing new collides with what's already there.
EnglishSet up claude-prospector's plugin-owned Python venv. Invoked via /setup-prospector or natural-language triggers: "set up claude-prospector", "install prospector dependencies", "prospector isn't working", "fix prospector", "repair prospector". Do not trigger on "dashboard", "usage analysis", or "skill adoption" — those are distinct skills.
EnglishUse when the user asks an interpretive question about their Claude Code token spend — budget status across the 5h / 7d / Sonnet-7d billing buckets, which agents/skills/projects are eating their budget, model-distribution drift, or what to change to reduce spend. Regenerates the claude-prospector dashboard as needed and reads the embedded data to answer. Do NOT use for bare "regenerate the dashboard" requests with no question attached (use usage-dashboard instead). Trigger phrases: "am I close to my Claude limit", "how much Sonnet am I using", "where are my Claude tokens going", "what's eating my Claude budget", "which agent uses the most tokens", "why is my Claude spend so high".
EnglishUse when the user explicitly asks to regenerate, rebuild, or refresh the claude-prospector token-usage dashboard with no interpretive question attached — runs python -m claudeprospector dashboard, writes the HTML file, and reports the output path. Do NOT use when the user is asking what the data means, where their budget stands, or what to change (use usage-analysis instead — it regenerates as part of answering). Trigger phrases: "regenerate the usage dashboard", "rebuild my claude-prospector dashboard", "refresh the token dashboard", "regen the prospector dashboard".
English
AGENT SKILLS ATLASIncludes Claude Audit, Setup Prospector, Usage Analysis, and other workflows.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Claude Audit
Audit a project's effective Claude Code configuration — custom and plugin-provided agents and skills — and produce 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 my agents duplicates", "what's redundant in my setup", or any similar request to review the agent/skill surface for the current project. Also trigger after a fresh plugin install when the user wants to verify nothing new collides with what's already there.
Setup Prospector
Set up claude-prospector's plugin-owned Python venv. Invoked via /setup-prospector or natural-language triggers: "set up claude-prospector", "install prospector dependencies", "prospector isn't working", "fix prospector", "repair prospector". Do not trigger on "dashboard", "usage analysis", or "skill adoption" — those are distinct skills.
Usage Analysis
Use when the user asks an interpretive question about their Claude Code token spend — budget status across the 5h / 7d / Sonnet-7d billing buckets, which agents/skills/projects are eating their budget, model-distribution drift, or what to change to reduce spend. Regenerates the claude-prospector dashboard as needed and reads the embedded data to answer. Do NOT use for bare "regenerate the dashboard" requests with no question attached (use usage-dashboard instead). Trigger phrases: "am I close to my Claude limit", "how much Sonnet am I using", "where are my Claude tokens going", "what's eating my Claude budget", "which agent uses the most tokens", "why is my Claude spend so high".
Usage Dashboard
Use when the user explicitly asks to regenerate, rebuild, or refresh the claude-prospector token-usage dashboard with no interpretive question attached — runs python -m claudeprospector dashboard, writes the HTML file, and reports the output path. Do NOT use when the user is asking what the data means, where their budget stands, or what to change (use usage-analysis instead — it regenerates as part of answering). Trigger phrases: "regenerate the usage dashboard", "rebuild my claude-prospector dashboard", "refresh the token dashboard", "regen the prospector dashboard".
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Claude Audit skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.