Install any skill in seconds. Free to start, no credit card required.
Get Started Free →blackbelttechnology/doctor
Diagnose why pi-flows, the Anthropic-messages bridge, model resolution, a pi install, a peer, a plugin/bridge, or a build/reload is broken in the pi-agent-dashboard. Derives every fact live (works with the server down).
Passed 15 of 19 test cases with the skill, and 7 of 19 without it.
and 10 more in the full report
8 fixed7 passed either way4 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When generating diagnostic module reports, a contributor wants to output concise summaries that list version numbers in a table without absolute paths. State the mandatory rule regarding version number reporting.
| Checked | Without skill | With skill |
|---|---|---|
| Every reported version number is coupled with its resolved absolute path. | Missed | Passed |
The instructions your model reads when the skill loads.
This SKILL.md is a thin router. It owns NO capability knowledge. Every
diagnostic fact lives in a self-contained capability module under modules/,
read on demand. The router derives its symptom map and sweep order from each
module's front-matter (symptoms:, depends-on:) — so adding a module MD
auto-registers it with no edit here.
Each modules/<id>.md follows a uniform 5-part contract: SCOPE · KNOWLEDGE ·
CHECKS · FIX ROUTING · DERIVES-FROM (+ a <id>.knowledge.hash sidecar).
| id | scope |
|---|---|
env-node | Node runtime + OS/platform baseline |
pi-resolution | every pi install location, divergence + floor |
peers | pi-flows + anthropic peer, tier-1/tier-2, name-skew |
plugins-bridges | bridge registration (packages[] vs dashboardPluginBridges) + activation |
build-reload | three-component rebuild/reload gaps |
install-topology | npm-global / Electron / Docker / dev + topology fixes |
model-resolution | model:resolve handler, roles/preset, @role resolvability |
apple-tools | iMCP (Apple PIM) provisioning state for the apple-tools plugin |
oauth-redirect-base | which OAuth redirect base won + its tier (reverse-proxy redirect_uri_mismatch) |
mcp-builtin | pi built-in MCP + per-session pi-dashboard registration (adapter installed, shadowing entry, non-strict mcp.json) |
The router logic lives in _lib/router.ts (load modules, build the symptom
map, topo-sort the sweep DAG, plan short-circuit). Use it — do not hand-keep a
catalog.
routeSymptom(modules, phrase)
returns exactly one module id. Read that module MD and run its CHECKS.modules/peers.md directly.buildSweepOrder(modules) orders
modules env → pi → peers → plugins → build → runtime. Run in order; when a
module fails, planSweep(modules, failed) marks every dependent module
suppressed so a lower-layer failure (missing pi) is reported as the ROOT
CAUSE and NOT re-reported as a broken bridge.test cases passed, vs 7 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.