← ClaudeAtlas

doctorlisted

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".
crisandrews/ClawCode · ★ 56 · AI & Automation · score 84
Install: claude install-skill crisandrews/ClawCode
# 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:create` or `/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 1. Call the MCP tool `agent_doctor` with `action='check'` (or `action='fix'` when the user passes `--fix`) 2. The tool returns a structured report; pass it through as-is (the tool already formats a card) 3. Supplement with cron status from `CronList` — the MCP server cannot see Claude Code's cron state, so include that here ## Steps ### Step 1 — Detect mode - If the user's message contains `--fix` or `/agent:doctor fix` or says "arreglar" / "auto-fix" / "repara" → mode is `fix` - Otherwise → mode is `check` ### Step 2 — Run the MCP tool Call: ``` agent_doctor(action='<mode>') ``` Print the returned card verbatim. ### Step 3 — Add cron status `agent_doctor` cannot read Claude Code's cron list (MCP servers don't have access