agentleFS
crisandrewscrisandrews/ClawCode/skills/doctor/SKILL.md

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

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.
  • AnthropicSkill

    uninstall

    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

  • woosikkimSkill

    cancel

    Clear any stale OMC-Slim state

    Also in 3 projects that use this

  • ibahgatSkill

    mode

    Inspect or switch omi operating mode/profile for speed, depth, autonomy, or strict quality gates.

    Also in 3 projects that use this

  • BlockSkill

    open

    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

  • QinghongLinSkill

    editor

    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

  • MicrosoftSkill

    init

    Also in 7 projects that use this

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
  1. Distinctive:

    When memory search returns nothing or feels wrong — check SQLite integrity

    line 17
  2. Distinctive:

    When heartbeats don't seem to fire — verify crons and active hours

    line 18
  3. Distinctive:

    When you enabled the HTTP bridge but the browser can't connect — probe it

    line 19
  4. Very specific:

    Call the MCP tool agent_doctor with action='check' (or action='fix' when the user passes --fix).

    line 25
  5. Very specific:

    If the user's message contains --fix or /agent:doctor fix or says "arreglar" / "auto-fix" / "repara" → mode is fix

    line 33
  6. Very specific:

    Call CronList() and pipe its FULL output (verbatim, including a literal No scheduled jobs.) to the mechanical auditor:

    line 46
  7. Very specific:

    Heartbeat cron: look for a job whose prompt contains /agent:heartbeat → report schedule

    line 68
  8. Very specific:

    Dreaming cron: look for a job whose prompt contains dream → report schedule

    line 69
  9. Very specific:

    If either is missing, show ⚠️ and suggest: "Missing cron — run the default crons flow (see AGENTS.md)"

    line 70
  10. Very specific:

    If the audit line reported orphaned>0, add: ⚠️ <N> registry reminder(s) not firing — run /agent:crons reconcile

    line 71
  11. Very specific:

    If the audit printed blocked key= lines, add: ⚠️ <B> reminder(s) with ambiguous live duplicates — review with /agent:crons list

    line 72
  12. Very specific:

    If the diagnostic card includes any → hint: lines, those are already rendered.

    line 85
  13. Very specific:

    After a fix run, if any fix was applied or any hook-related issue remains, recommend /mcp to reload the MCP server.

    line 89
  14. Very specific:

    Do NOT run auto-fixes without the user asking.

    line 103
  15. Very specific:

    Do NOT invent diagnostic categories not implemented in lib/doctor.ts.

    line 104

“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.

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

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. Refresh the cron audit FIRST — CronList → writeback.sh audit — so the registry's .audit state is current
  2. Call the MCP tool agent_doctor with action='check' (or action='fix' when the user passes --fix); its cron-registry check reads the .audit you just refreshed
  3. The tool returns a structured report; pass it through as-is (the tool already formats a card)
  4. Supplement with cron status rendered from the same CronList output — the MCP server cannot see Claude Code's cron state

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 — 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 prompt contains /agent:heartbeat → report schedule
  • Dreaming cron: look for a job whose prompt contains dream → 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/5

Step 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 --fix or 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 consult docs/doctor.md for the current check list.

References

  • docs/doctor.md — full feature documentation
  • lib/doctor.ts — implementation (checks + fixes)
  • docs/INDEX.md — master feature index

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.