Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add preset-io/agent-skills --skill preset-mcp-troubleshootinggit clone --depth 1 https://github.com/preset-io/agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/preset-io/agent-skills/preset-mcp-troubleshooting)<a href="https://agentmods.dev/skills/preset-io/agent-skills/preset-mcp-troubleshooting"><img src="https://agentmods.dev/badge/skills/preset-io/agent-skills/preset-mcp-troubleshooting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/preset-io/agent-skills/preset-mcp-troubleshooting"><img src="https://agentmods.dev/badge/skills/preset-io/agent-skills/preset-mcp-troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.00399 |
| Opus 5.5 | $0.00017 | $0.00160 |
| Sonnet 5.5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
preset-mcp-troubleshooting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 17d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
preset-mcp-troubleshooting
Use when Superset MCP tools fail, return validation errors, return permission errors, or produce oversized responses.
Always
- Stay on MCP troubleshooting; do not switch to direct APIs.
- Use
health_checkfirst for service availability on a direct connection. On the Preset gateway,health_checkis a workspace tool reached throughcall_tool; followpreset-mcp-gatewayfor gateway authentication, scope, workspace, and service failures. - Use
generate_bug_reportwhen the user says MCP is broken or asks how to report an issue. - Treat permission denied as authoritative.
- No permission workaround: do not search alternate tools, REST APIs, or direct APIs to expose restricted data.
- Use live tool schemas to fix validation errors.
Decision Rules
- Connection or availability issue:
health_check. - Tool parameter/schema issue: inspect the live tool schema and retry only with corrected MCP arguments.
- Permission issue: explain the denied operation and stop; do not search for alternate tools to expose restricted data.
- Response too large: rerun with narrower filters, identifiers, page sizes, or row limits.
- Repro/report request:
generate_bug_report.
Workflow Order
- Classify the failure: availability, validation, permission, unsupported capability, oversized response, or unknown error.
- Use the smallest diagnostic MCP tool.
- Explain the failure in user terms.
- For permission denied, stop or generate bug report when requested.
- Stop before direct API or REST API calls.
- Retry only when the correction is clear and remains on MCP.
Retrieve
- Troubleshooting guide: references/troubleshooting.md
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 17d ago Changed 6849f91fbf7c
- 1mo ago First seen · 39 lines · 42 tokens per session scan A 76e57d2d44ca
preset-mcp-troubleshooting is a skill published in the GitHub repository preset-io/agent-skills (13 stars, last pushed 18d ago), licensed Apache-2.0. It adds 42 tokens to every session and 399 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
bug-report
Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.
openclaw-debugger
Trigger when an OpenClaw agent is broken, silent, crashing, stuck, not responding, returning empty output, or the user says "my agent is down", "agent not working", "/openclaw-debugger". Walks through the standard OpenClaw 2026.4 diagnosis checklist and prints a report.