agentleFS
amtiYoamtiYo/agents/.agents/skills/mcp-troubleshooting/SKILL.md

mcp-troubleshooting

Skill103 starsChanged 2 months agoApache-2.0View on GitHub

Diagnose and fix MCP configuration/runtime issues across supported integrations using agents CLI checks.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. IrMaho/TeleDOM★ 10same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When MCP servers are failing or not visible:

    line 6
  2. Very specific:

    Run agents status --fast to inspect configured vs enabled integrations.

    line 8
  3. Very specific:

    Run agents mcp test for schema/config validation.

    line 9
  4. Very specific:

    Run agents mcp test --runtime to check integration CLI/runtime connectivity.

    line 10
  5. Very specific:

    Run agents doctor for environment and binary diagnostics.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When MCP servers are failing or not visible:

  1. Run agents status --fast to inspect configured vs enabled integrations.
  2. Run agents mcp test for schema/config validation.
  3. Run agents mcp test --runtime to check integration CLI/runtime connectivity.
  4. Run agents doctor for environment and binary diagnostics.
  5. Apply the smallest safe fix, then run agents sync and verify with agents sync --check.

Troubleshooting priorities:

  • Missing binaries or PATH issues.
  • Invalid server names/transport fields.
  • Missing required environment variables or secrets.
  • Target mismatch (server not routed to expected integration).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.