How do I install the Loop Doctor skill?

Run npx skillmds@latest add cbdreamer11/loop-doctor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Loop Doctor safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Loop Doctor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Loop Doctor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Loop Doctor?

cbdreamer11 (@cbdreamer11) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Loop Doctor by cbdreamer11 — Agent Skill

Name: Loop Doctor
Author: cbdreamer11

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.

cbdreamer11 4502fec 2.1 KB Updated Sep 17, 2026

File contents

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.

---name: loop-doctordescription: 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.---# DoctorVerify the installation the same way the method verifies everything else: byobserving, 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 itis 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** andreport which ones still work. A verification contract with a stale build command isworse than none, because it produces confident green nonsense.## 3 · The connectionsRe-run the connection table from session 0: build, browser, database, payments testmode, git remote. PASS / FAIL / ABSENT. Every ABSENT should already be a declaredGAP in `.loop/VERIFY.md`; if it is not, add it.## 4 · The effort this session is really running atThis session's effort level: **${CLAUDE_EFFORT}**If that shows a level, that is the real one — including any silent downgrade. If itprinted the placeholder literally, this version does not interpolate it; run`echo "$CLAUDE_EFFORT"` in a shell instead. There is deliberately no equivalent forthe model: **no session can read which model it is running on**, so do not print aguess. If the role matters, relaunch with `./loop <role>` and trust the profile.## 5 · VerdictOne table: what is healthy, what is broken with the exact command to fix it, andwhat is absent by design. If anything in section 1 or 2 is broken, say plainly thatthe method is **not** in force in this project yet.

Frequently asked questions