debug
Debug issues in the MCP Gateway Registry using first-principles thinking. Invoke when something is broken, timing out, returning errors, or behaving unexpectedly. Forces structured root-cause analysis before any code change is proposed.
npx skills add agentic-community/mcp-gateway-registry --skill debug --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Debug Skill Use this skill when debugging any issue in the MCP Gateway Registry: timeouts, 5xx errors, UI failures, broken flows, unexpected behavior. Invoke this skill proactively whenever normal debugging is failing or going in circles, or use it from the start for any non-trivial issue. We are testing whether this approach should be the default for all debugging. ## Expert Personas Before starting, announce that you are consulting the following expert panel. Each persona challenges assumptions and contributes their domain expertise: - **SRE/Infrastructure Engineer** - Thinks about: single-worker bottlenecks, event loop blocking, connection pooling, DNS resolution, proxy timeouts, container resource limits, startup ordering. - **Frontend/Browser Security Engineer** - Thinks about: same-origin vs cross-origin, preflight behavior, cookie scope, session validity after restarts, browser caching of error responses, service worker interception. - **Backend/Python Engineer** - Thinks about: asyncio event loop blocking, synchronous HTTP calls on async workers, Pydantic model_dump dropping extra fields, DB write ordering, exception swallowing in try/except. - **Senior Staff Engineer (Sk
- Expert Personas
- First Principles Debugging
- Step 1: Reproduce and observe (do NOT theorize yet)
- Step 2: Check what the worker is DOING right now
- Step 3: Is this new or pre-existing?
- Step 4: If you see something suspicious in the logs, ask HOW it connects
- Step 5: Before proposing a code change, answer these questions
- Step 6: Cross-question your own theory
- Anti-patterns to avoid
- Debugging checklist (copy into your response)
docker compose logs registry --since=30s 2>&1 | tail -30
What does the debug skill do?
Debug issues in the MCP Gateway Registry using first-principles thinking. Invoke when something is broken, timing out, returning errors, or behaving unexpectedly. Forces structured root-cause analysis before any code change is proposed.
How do I install it?
Run `npx skills add agentic-community/mcp-gateway-registry --skill debug --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agentic-community/mcp-gateway-registry, a repository with 845 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.