Skip to content
Development
Skill

/loop-doctor

Checks that the loop is actually installed and working in this project - files present, role profiles valid, connections alive, effort level real. Use after setup, after an upgrade, or when something behaves as if the method is not loaded.

From plugin
loop-kit
87 skills6 agents2 hooks
Install
$ npx -y skills add cbdreamer11/CB-loop-kit-claude-plugin --skill loop-doctor --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/loop-doctor

Context preview

The summary Claude sees to decide when to auto-load this skill.

Checks that the loop is actually installed and working in this project - files present, role profiles valid, connections alive, effort level real. Use after setup, after an upgrade, or when something behaves as if the method is not loaded.

SKILL.md

loop-doctor.SKILL.md
name: loop-doctor
description: Checks that the loop is actually installed and working in this project - files present, role profiles valid, connections alive, effort level real. Use after setup, after an upgrade, or when something behaves as if the method is not loaded.

Doctor

Verify the installation the same way the method verifies everything else: by observing, not by assuming it took.

1 · The files

`ls -la .loop/ .loop/roles/ .claude/agents/ 2>&1` and confirm: `STATE.md`, `VERIFY.md`, `DECISIONS.md`, `GOTCHAS.md`, the four role profiles, the `loop` wrapper (and that it is executable), and the role agents in the project's `.claude/agents/`.

Report anything missing, and whether `.loop/ACCESS.local.md` is gitignored — if it is tracked, stop and say so loudly: it is the file most likely to hold a credential.

2 · The contract is still true

`.loop/VERIFY.md` rots faster than anything else. **Run each declared command** and report which ones still work. A verification contract with a stale build command is worse than none, because it produces confident green nonsense.

3 · The connections

Re-run the connection table from session 0: build, browser, database, payments test mode, git remote. PASS / FAIL / ABSENT. Every ABSENT should already be a declared GAP in `.loop/VERIFY.md`; if it is not, add it.

4 · The effort this session is really running at

This session's effort level: **${CLAUDE_EFFORT}**

If that shows a level, that is the real one — including any silent downgrade. If it printed the placeholder literally, this version does not interpolate it; run `echo "$CLAUDE_EFFORT"` in a shell instead. There is deliberately no equivalent for the model: **no session can read which model it is running on**, so do not print a guess. If the role matters, relaunch with `./loop <role>` and trust the profile.

5 · Verdict

One table: what is healthy, what is broken with the exact command to fix it, and what is absent by design. If anything in section 1 or 2 is broken, say plainly that the method is **not** in force in this project yet.

Read more
Ships withloop-kit

A working method for building real software with coding agents, across many sessions.

Get the whole plugin
Stats
8
Stars
1
Forks
Maintained
Maintenance
Shell
Language
MIT
License
1mo ago
Last commit
1mo ago
Created

Repo: cbdreamer11/CB-loop-kit-claude-plugin

Other skills on loop-kit.

loop
Skill

loop

The build loop - locate yourself, investigate the real code, build one slice completely, verify it for real, fix and re-verify, then close and hand off. Use…