doctor
Skill64 starsChanged 2 months agoMITView on GitHub
Run diagnostic checks on the agent workspace. Triggers on /agent:doctor, "diagnóstico", "diagnostico", "doctor", "health check", "agent health", "checkup", "revisar agente", "agent broken", "fix agent", "revisa el agente".
81 other projects use a version of this.
Adopted by
Most recently taken up by
- JanSzewczyk/spec-driven-developmenttheir own version, first seen Nov 8, 2026
- stunt-double/stuntdouble-mcptheir own version, first seen Nov 8, 2026
- aaroncohn/openspec-conductor-powerupstheir own version, first seen Nov 8, 2026
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- woosikkim/oh-my-claudecode-slimtheir own version, first seen Nov 8, 2026
- Ubuntu-Buddha/claude-code-stranger-dangertheir own version, first seen Nov 8, 2026
Used with
Projects with it also use uninstall, cancel and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkilluninstall
Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.
Also in 6 projects that use this
woosikkimSkillcancel
Clear any stale OMC-Slim state
Also in 3 projects that use this
ibahgatSkillmode
Inspect or switch omi operating mode/profile for speed, depth, autonomy, or strict quality gates.
Also in 3 projects that use this
BlockSkillopen
Open markdown documents in Penpal for collaborative review. Use when you want a human to review a document, plan, or research artifact.
Also in 3 projects that use this
QinghongLinSkilleditor
Read analyst.json and detective.json, make all editorial decisions — what the blog argues, which findings matter, narrative arc and section structure. No visual design. Outputs editor.md (prose) and editor.json (structure with edt_xx IDs).
Also in 3 projects that use this
MicrosoftSkillinit
Also in 7 projects that use this
Other versions81 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 81
- Yeachan-Heo/oh-my-codex★ 34ksame name
- jihe520/MathModelAgent★ 6.2ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
- fakechris/obsidian_vault_pipeline★ 165same name
- NoobyGains/godmode★ 118same name
- Rich627/whatsapp-claude-plugin★ 114same name
- bluzir/claude-code-design★ 102same name
- jjanczur/tyran★ 81same name
- svy04/ballast★ 73same name
- Hainrixz/agente-pagokit★ 68same name
71 more not listed
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 repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- aboutSkill
- channelsSkill
- compactSkill
- createSkill
- cronsSkill
- heartbeatSkill
- helpSkill
- importSkill
- liveSkill
- messagingSkill
- newSkill
- scopeSkill
- serviceSkill
- settingsSkill
- skill-managerSkill
- statusSkill
- updateSkill
- usageSkill
- voiceSkill
- whoamiSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 3 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 61 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
When memory search returns nothing or feels wrong — check SQLite integrity
- Distinctive: line 18
When heartbeats don't seem to fire — verify crons and active hours
- Distinctive: line 19
When you enabled the HTTP bridge but the browser can't connect — probe it
- Very specific: line 25
Call the MCP tool agent_doctor with action='check' (or action='fix' when the user passes --fix).
- Very specific: line 33
If the user's message contains --fix or /agent:doctor fix or says "arreglar" / "auto-fix" / "repara" → mode is fix
- Very specific: line 46
Call CronList() and pipe its FULL output (verbatim, including a literal No scheduled jobs.) to the mechanical auditor:
- Very specific: line 68
Heartbeat cron: look for a job whose prompt contains /agent:heartbeat → report schedule
- Very specific: line 69
Dreaming cron: look for a job whose prompt contains dream → report schedule
- Very specific: line 70
If either is missing, show ⚠️ and suggest: "Missing cron — run the default crons flow (see AGENTS.md)"
- Very specific: line 71
If the audit line reported orphaned>0, add: ⚠️ <N> registry reminder(s) not firing — run /agent:crons reconcile
- Very specific: line 72
If the audit printed blocked key= lines, add: ⚠️ <B> reminder(s) with ambiguous live duplicates — review with /agent:crons list
- Very specific: line 85
If the diagnostic card includes any → hint: lines, those are already rendered.
- Very specific: line 89
After a fix run, if any fix was applied or any hook-related issue remains, recommend /mcp to reload the MCP server.
- Very specific: line 103
Do NOT run auto-fixes without the user asking.
- Very specific: line 104
Do NOT invent diagnostic categories not implemented in lib/doctor.ts.
“Common” is measured: kept by at least 6 in 10 of the 61 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Doctor
Health check for this agent. Inspects config, identity, memory, SQLite index, QMD, crons, hooks, HTTP bridge, messaging plugins, and dreaming. When invoked with --fix, applies safe auto-repairs (create memory dir, sync index, delete stale BOOTSTRAP.md) before re-running checks.
This is a CORE feature — always available. See docs/doctor.md for the full list of checks and auto-fixes.
When to use
- Right after
/agent:createor/agent:import— verify setup is clean - When memory search returns nothing or feels wrong — check SQLite integrity
- When heartbeats don't seem to fire — verify crons and active hours
- When you enabled the HTTP bridge but the browser can't connect — probe it
- Anytime something feels off
How it works
- Refresh the cron audit FIRST —
CronList→writeback.sh audit— so the registry's.auditstate is current - Call the MCP tool
agent_doctorwithaction='check'(oraction='fix'when the user passes--fix); its cron-registry check reads the.audityou just refreshed - The tool returns a structured report; pass it through as-is (the tool already formats a card)
- Supplement with cron status rendered from the same
CronListoutput — the MCP server cannot see Claude Code's cron state
Steps
Step 1 — Detect mode
- If the user's message contains
--fixor/agent:doctor fixor says "arreglar" / "auto-fix" / "repara" → mode isfix - Otherwise → mode is
check
Step 2 — Refresh the cron audit (BEFORE the card)
The agent_doctor card reads the registry's persisted .audit offline. Refresh it first, or the card may render stale/contradictory cron state.
CronList is a deferred tool. Load it first:
ToolSearch(query='select:CronList')Call CronList() and pipe its FULL output (verbatim, including a literal No scheduled jobs.) to the mechanical auditor:
printf '%s\n' "<full CronList output>" | bash "$CLAUDE_PLUGIN_ROOT/skills/crons/writeback.sh" audit(Exit 4 = CronList format drift — remember it and report it as its own ⚠️ line in Step 4.) Keep the CronList output for Step 4.
Step 3 — Run the MCP tool
Call:
agent_doctor(action='<mode>')Print the returned card verbatim.
Step 4 — Add cron status
Append a cron section rendered from the Step 2 CronList output (do not call it again):
- Heartbeat cron: look for a job whose
promptcontains/agent:heartbeat→ report schedule - Dreaming cron: look for a job whose
promptcontainsdream→ report schedule - If either is missing, show
⚠️and suggest: "Missing cron — run the default crons flow (see AGENTS.md)" - If the audit line reported
orphaned>0, add:⚠️ <N> registry reminder(s) not firing — run /agent:crons reconcile - If the audit printed
blocked key=lines, add:⚠️ <B> reminder(s) with ambiguous live duplicates — review with /agent:crons list
Format:
Crons:
✅ Heartbeat: */30 * * * *
✅ Dreaming: 0 3 * * *
✅ Registry audit: alive=5/5Step 5 — Surface hints
If the diagnostic card includes any → hint: lines, those are already rendered. Do not repeat them; the user has what they need.
Step 6 — If in fix mode, remind the user to reload
After a fix run, if any fix was applied or any hook-related issue remains, recommend /mcp to reload the MCP server. Example:
Some changes take effect only after reloading the MCP server. Run `/mcp` to apply.Response style
- Terse. No preamble. Just the card + cron section + optional reload hint.
- On messaging channels (WhatsApp, Telegram, Discord), collapse the card to one line per check:
✅ Config · ✅ Identity · ⏸️ HTTP · ℹ️ Dreaming · ...— full card is too wide for mobile. - On CLI or WebChat, keep the full multi-line card.
Never
- Do NOT run auto-fixes without the user asking. If they say
/agent:doctor, only check. Only apply fixes on--fixor when the user explicitly asks to repair. - Do NOT invent diagnostic categories not implemented in
lib/doctor.ts. If they ask about something not covered (e.g. "check my OpenAI API key"), say the doctor doesn't cover that yet — or consultdocs/doctor.mdfor the current check list.
References
docs/doctor.md— full feature documentationlib/doctor.ts— implementation (checks + fixes)docs/INDEX.md— master feature index
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
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.

