agentleFS
Sign inStart free
NoobyGainsNoobyGains/godmode/skills/doctor/SKILL.md

doctor

Skill115 starsChanged 7 days agoMITView on GitHub

Use when GodMode skills do not seem to trigger, when the user asks whether GodMode is installed or working, or after installing or updating the plugin on any harness

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 56 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:

    No exceptions. No workarounds.

    line 17
  2. Distinctive:

    If the script itself cannot run, report the exact error and the install root you derived.

    line 35
  3. Distinctive:

    Run the script from the derived install root

    line 65

“Common” is measured: kept by at least 6 in 10 of the 56 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

Checks the GodMode installation from inside the running harness and reports what it finds. The bootstrap that makes skills trigger is injected at session start; when it is missing, every other skill is inert, so this check comes first.

The Prime Directive

DIAGNOSE THE INSTALL BEFORE BLAMING THE SKILLS

No exceptions. No workarounds. No shortcuts.

When to Use

Required:

  • The user asks "is GodMode working?", "why didn't GodMode activate?", or runs the doctor command
  • Right after installing or updating GodMode on a new harness or machine
  • Skills that should have fired (design before code, verification before "done") did not

Skip:

  • Everything else; this skill only inspects the install

The Protocol

  1. Locate the install root. It is the directory that contains the skills/ folder holding this file. Do not guess a path from memory; derive it from where this skill was loaded.
  2. Run the doctor script with the shell: <install-root>/hooks/run-hook.cmd doctor. On Windows without Git Bash the wrapper exits silently with no output; say so and point the user at installing Git for Windows.
  3. Read every line of the output. ok lines pass, FAIL lines are the problem, info lines describe the environment (harness, platform, version).
  4. Report the harness and version detected, each failure with the fix the script printed, and whether a fresh session is needed (the bootstrap only injects at session start).
  5. If the script itself cannot run, report the exact error and the install root you derived. Do not claim the install is healthy without the script's output.

What the script checks

CheckWhy it matters
skills/using-godmode/SKILL.md readableThe session-start hook injects this file; without it nothing triggers
Skill count above 20A partial install or a wrong root
Hook scripts executable and LF-terminatedGodMode 1.0 shipped without the executable bit, so the hook never ran (issues #1, #2, #4)
hooks.json quotes the plugin rootSingle quotes stop the variable from expanding
session-start prints the Claude Code JSON shapeThe hook's output is what the harness reads

Cognitive Traps

RationalisationTruth
"Skills exist on disk, so GodMode is installed"Files on disk do nothing until the bootstrap reaches the model
"The hook probably ran"Run the script; its output is the only evidence
"I remember the install path"Paths differ per harness and version folder; derive it from this file
"It worked last session"Plugin updates change the install folder; recheck after every update
"No output means no problem"No output means the wrapper could not find bash; that is a failure to report

Guardrails

Never:

  • Declare the install healthy without the script's output in this session
  • Edit the user's harness settings to "fix" things; report and let the user decide
  • Guess a harness from the prompt text; read the info harness line

Always:

  • Run the script from the derived install root
  • Quote failures verbatim with the printed fix
  • Say whether a new session is needed

Connections

  • godmode:using-godmode: the bootstrap this skill verifies is present
  • godmode:environment-awareness: when the failure is a shell or platform problem rather than an install problem

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.

Reviews can't be read right now.

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