agentleFS
aaroncohnaaroncohn/openspec-conductor-powerups/skills/doctor/SKILL.md

doctor

Skill1 starsChanged 11 days agoMITView on GitHub

Check that the plugin is current and that babysitter can work here. Compares the installed plugin and this session's copy with the latest release, checks gh, openspec, the repo's ## babysitter defaults, and (locally) Conductor's database and the outbox table babysitter writes to, or (in the cloud) the conductor CLI's token and which workspaces predate the latest release. Read-only. Use when the user runs `/babysitter:doctor`, asks "am I on the latest version?", "why isn't `/babysitter:x` showing?", or before a babysitter run.

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

3 rules. 0 are common, 3 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run it and show its table:

    line 8
  2. Distinctive:

    If any row is ⛔, say what to do first.

    line 16
  3. Distinctive:

    Don't fix anything yourself.

    line 22

“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 it and show its table:

python3 <this skill's dir>/doctor.py

Add --send-test when the user asks whether babysitter's messages will show in the workspace chats, or after a Conductor update: it sends one message to this session through babysitter's local path and reports whether it landed (it shows up in this chat as "Via Babysitter: doctor test"; that's expected). It prints one row per check: ✓ fine, ⚠ worth knowing, ⛔ needs a fix, with the fix in the last column. Below the table, in plain words:

  • If any row is ⛔, say what to do first. "This session runs an older copy" means: start a new session in this workspace, nothing else. A version mismatch means: run the update line, then a new session.
  • In the cloud, workspaces "created before the latest release" are only a guess from dates: say so, and that only workspaces where the user types /babysitter: commands need the install; queue and change workspaces are driven by messages and don't.
  • An "organization switcher" ⛔ means Conductor is on a cloud organization: the Create dialog that new-batch-explore and babysitter open would make cloud workspaces on another repo. The fix is the switcher at the top left of Conductor.
  • An "installed after this workspace was created" ⛔ (cloud) means the plugin was installed after the workspace's first session started, by a SessionStart hook or by a Setup script that failed or was still running. The user should make sure the repository's Setup script has the install line (Conductor's cloud organization settings, not .conductor/settings.toml). If it already does, they should check that script's output in a fresh workspace for errors or slowness. Meanwhile: type the full /babysitter:… name, which works even when the picker doesn't list it. The picker catches up after a few sessions.
  • An outbox-table or send-test ⛔ means a Conductor update changed its database or messaging. Babysitter still works, falling back to Claude's SendMessage (messages won't show in the workspace chats). Suggest opening an issue on the plugin with the doctor output.

Don't fix anything yourself; the fixes touch the user's Claude config and Conductor settings.

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.