agentleFS
Sign inStart free
edenbuildsedenbuilds/agentloop/.agents/skills/doctor/SKILL.md

doctor

Skill0 starsChanged 4 months agoMITView on GitHub

Diagnose missing agentloop setup, connectivity, and configuration before long runs. Use at session start, after install, or when Overmind/plan/memory/MCP looks broken.

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 10 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

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 15 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run early. Surface missing setup before burning a Conductor budget.

    line 8
  2. Very specific:

    Prefer running scripts/doctor.sh when available, then interpret.

    line 22
  3. Distinctive:

    Never invent green CI or working MCP.

    line 49
  4. Distinctive:

    Do not modify production systems.

    line 50
  5. Distinctive:

    Keep the report short enough to read in one screen.

    line 51

“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

Run early. Surface missing setup before burning a Conductor budget.

Checks (in order)

  1. Plugin surface — scripts/validate.sh (or equivalent) for skills/commands/agents/rules manifests.
  2. Repo harness files — AGENTS.md, rules, commands, skills present.
  3. .agentloop/ state — exists? has handoff/plan/stop? stale?
  4. Templates — templates/.agentloop/* available for scaffold.
  5. Verify toolchain — detect package manager / test / lint / typecheck commands; note gaps.
  6. Git — repo clean/dirty; dangerous state (detached, mid-rebase).
  7. Hooks — hooks/hooks.json + scripts/session-start.sh executable.
  8. Memory connectivity — .agentloop/memory.md writable; Supermemory/MCP memory tool reachable (if configured). Report missing without inventing.
  9. Adapters — note which IDE adapters exist under adapters/.

Prefer running scripts/doctor.sh when available, then interpret.

Output format

# Doctor report
Status: green | yellow | red

## Blocking
- …

## Warnings
- …

## OK
- …

## Recommended fixes
1. …
  • red — do not start expensive Execute; fix blockers or get explicit override
  • yellow — plan allowed; disclose risks in Conductor §6
  • green — clear for Conductor → approval → Execute

Guardrails

  • Never invent green CI or working MCP.
  • Do not modify production systems; diagnose and propose.
  • Keep the report short enough to read in one screen.

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.

Check your setup, free