← ClaudeAtlas

mcp-migration-auditorlisted

Iterate-stage skill: scans an MCP configuration against the 2026 spec revision and returns per-server BREAKS/DEGRADED/SAFE verdicts — every finding citing both the config line and the spec clause. Use when spec readiness is the question — 'audit our MCP config for the 2026 spec', 'will our connectors break when the spec lands', 'spec-readiness scan on this .mcp.json' — or when /pm routes such a request here. Do NOT use for MCP context-cost audits, for debugging broken connections, for server installation, or for what-changed-in-the-spec questions with no config to audit.
Abhillashjadhav/PM-agent-OS · ★ 1 · AI & Automation · score 60
Install: claude install-skill Abhillashjadhav/PM-agent-OS
# MCP Migration Auditor Config on one side, spec on the other, and every finding holds a line from each. A migration verdict that can't quote both is a guess wearing a checklist. ## Verification gates (defined first; output is blocked until all pass) - **G1 — Double citation:** every finding cites the config line(s) it applies to AND the spec clause it violates or satisfies — quoted, from the provided baseline or spec text actually fetched this session. One-sided findings fail. - **G2 — Spec honesty:** no clause is asserted that can't be quoted. Recollected-but-unquotable spec changes are tagged `unverified: confirm against current spec` and excluded from verdicts. Invented deprecation dates, clauses, or timelines fail. - **G3 — One verdict per server, fixes concrete:** each server gets exactly one of BREAKS / DEGRADED / SAFE; every non-SAFE finding carries the concrete fix (what the line becomes) and an effort class — "update it" is not a fix. ## Steps 1. **Number the config and inventory the servers:** transport, auth, capabilities per server — these are the audit's subjects, cited by line. 2. **Fix the spec baseline.** Use the user-provided baseline verbatim, or fetch the current spec/changelog text and quote from it. The baseline's clauses are the only law this audit applies; its version/date is stated in the header. 3. **Audit each server against each relevant clause:** transport (removed/replaced transports), auth (required patterns, deprecated token styles), capab