cli-over-mcp-auditorlisted

Use this skill proactively on the first substantial prompt of a session — silently inspect the session's own available tools/MCP servers (never ask the user to paste anything for this check) and, if any connectors look irrelevant to the task at hand, surface one compact line offering to free up context. Use this skill when the user makes explicit requests too — to audit MCP connectors, reduce context window usage, or explain why sessions run out of context fast — phrasings like "audit my MCPs for context cost", "why is my context filling up", "should I use CLI instead of MCP", "reduce my context overhead", "my sessions compact too early" — which get the full deep-audit flow instead of the one-liner. Do NOT use for debugging a broken MCP connection, for installing new connectors, for general questions about what MCP is, or for MCP spec-compatibility and migration audits (mcp-migration-auditor's job).
Abhillashjadhav/AI-PM-essential-skills · ★ 2 · AI & Automation · score 58

Install: claude install-skill Abhillashjadhav/AI-PM-essential-skills

# CLI-over-MCP Auditor Every connected MCP server loads its tool definitions into the context window at session start — a standing tax paid whether or not the tools are used. CLI tools cost zero context until invoked. This skill finds the tax and recommends where to stop paying it. ## Step 0 — First-prompt check (proactive, silent) On the first substantial prompt of a session, before doing anything else, silently inspect the session's own already-available tools/MCP servers — do not ask the user to run or paste `claude mcp list` for this check; that's only for the explicit deep-audit flow (Step 1). Count connected MCP servers and their tools directly from what's visible in the session. Judge relevance against the task the user is actually asking for right now — not against hypothetical future use. If one or more connectors look irrelevant to this task, emit exactly one line, then continue straight into the task: ``` N MCPs loaded, M unused for this work — disable to free up to ~X% context? ``` If nothing looks unused or irrelevant, say nothing — stay silent. This check runs once per session, not on every prompt. ## Step 1 — Inventory (explicit deep audit) List every connected MCP server. In Claude Code, ask the user to run `claude mcp list` and paste the output, or read `.mcp.json` / settings files if accessible. For each server, list its tools and count them. ## Step 2 — Estimate idle cost For each MCP server, estimate context cost as the token size of its injected