Loop doctor
Skill cbdreamer11/CB-loop-kit-claude-plugin/skills/loop-doctor
A session-based working method for coding agents: plan in thin complete slices, build one at a time, verify by observing real behaviour, hand off cleanly. Skills + agents + 2 hooks for Claude Code.
npx -y skills add cbdreamer11/CB-loop-kit-claude-plugin --skill loop-doctorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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
2.1 KB, 466 tokens by cl100k_base, as published. Nobody here has run it
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.