Claude Code Setup Audit: Skills, MCPs, CLAUDE.md
Audit your Claude Code skills, MCP servers, and CLAUDE.md: find overlaps, context bloat, and wrong scopes, with exact fix commands.
Before & after
Same prompt, same agent — the only difference is the skill.
You have several skills and MCPs installed across your Claude Code setup. Some are global (available everywhere) and some are scoped to specific projects. It would help to organize them so you know what's available and whether there are any redundancies or conflicts. You could make a list of all the skills, then another list of all the MCPs, and note which scope each one is at. That way you'll have a clear picture of what you've got. You might also want to think about which ones you actually use versus which ones you could remove. It's easy to accumulate tools and then forget about them, so a periodic audit can help you stay organized. I'd be happy to help you think through this, but you'd need to provide details about what you've installed.
CLAUDE CODE ORGANIZER DASHBOARD GLOBAL SCOPE (Installed everywhere) • Skills: karpathy-check, roast, marketing-council, cro (4 total) • MCPs: file-system, git, bash, web-fetch (4 total) PROJECT SCOPE: agentvolt • Skills: brand-voice-definer, saas-onboarding-emails, email-repurpose, ecom-launch-sequence (4 total) • MCPs: prisma (database), stripe (payments), neon (postgres) (3 total) PROJECT SCOPE: portfolio-site • Skills: wall-of-text-to-html, a11y-audit (2 total) • MCPs: figma (design system), netlify (deploy) (2 total) CONFLICTS DETECTED → Global cro + Project agentvolt saas-onboarding-emails both transform marketing copy; unclear priority UNUSED (No activity in 30 days) • financial-health (global) • obsidian-skills (project: portfolio-site) COUNT SUMMARY • Skills total: 10 (6 global + 4 project-scoped) • MCPs total: 9 (4 global + 5 project-scoped) • Recommended action: Archive obsidian-skills if Obsidian vault is no longer in use
About this skill
The wrong skill keeps triggering, two MCP servers do the same thing, and /context is half full before you type a word. You installed things one at a time and never looked at the whole picture. This skill audits your entire Claude Code setup across user, project, and local scope and gives you a cleanup plan you can roll back.
What it does
- Inventories skills, MCP servers, CLAUDE.md files, settings, subagents, and plugins by scope, with the shell commands to collect it all in one pass
- Finds skills whose descriptions compete for the same requests and rewrites them so they stop colliding
- Shows where your context actually goes (MCP tool schemas, the CLAUDE.md chain, skill descriptions), so you cut what costs tokens and leave what doesn't
- Uses your session transcripts to separate truly unused servers and skills from rarely used ones
- Catches scope mistakes: secrets committed in
.mcp.json, repo-specific rules in global CLAUDE.md, and team tools stuck in personal scope - Produces a back-up, disable, then delete plan with exact
claude mcpcommands and a rollback step
What you get
An audit report: an inventory table, findings ranked by impact (conflict, secret, bloat, scope, dead), rewritten skill descriptions where needed, and a command-by-command change plan with rollback.
Best for
Developers and team leads with dozens of skills, several MCP servers, or layered CLAUDE.md files who want Claude Code faster, more predictable, and safe to share with a team.
SKILL.md preview
---
name: claude-code-setup-audit
… (sign up to view the full skill)Featured in
More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.