A portable agent skill β works in Claude Code, Codex, Hermes, and OpenClaw β that interviews you and scaffolds a self-running autonomous loop, complete with verifier, state file, and human gate, so you don't build one wrong.
- Forgot to write a separate verifier (the agent judged its own work)
- Leaked changing state into the skill file (the loop lost memory between runs)
- Shipped a loop with no stop condition (it ran forever and burned budget)
loop-maker catches all three before you write a line.
π To build a loop, it asks you 7 things β one at a time:
1. Goal β what checkable condition means "done for now"? (a true/false test, not a vibe)
2. Trigger β what starts each run: a schedule, an event, or run-until-done?
3. Discovery β how does it find the work to do each round?
4. Action β what's it allowed to do, and through which tools?
5. Verificationβ who checks the result, and against what? (a separate judge)
6. State β where does "what's done / what's left" live, outside the chat?
7. Human gate β which actions are irreversible and must ask you first?
| What it does | Runs a 7-question wizard; catches missing verifiers, state leaks, and runaway loops before scaffold |
| What you get | A ready-to-run loop folder: SKILL.md + STATE.md + verifier script + stop condition wired in |
| How you start | /loop-maker, or just describe an automate/schedule/monitor task β fires without the word "loop" |
| Install | git clone β¦ ~/.claude/skills/loop-maker β or see Install below |
Q3/7 βββββββ 43%
---
π elicit β π survey β π― select β π scaffold
(you are here: π― select)
---
ββ LOOP BLUEPRINT ββββββββββββββββββββββββββββββββββββ
β GOAL β verifiable β
β TRIGGER schedule Β· 08:00 β
β VERIFY β separate script β
β STATE loops/<name>/STATE.md β
β GATES merge = human Β· budget 25/run β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββ
The progress bar, breadcrumb, and blueprint box are rendered live by scripts/loop_progress.py β a zero-dep Python 3 helper that ships with the skill.
ββββββββββββ ββββββββββββ ββββββββββββ ββββββββββββ
β elicit ββββββΆβ survey ββββββΆβ select ββββββΆβ scaffold β
β 7 Qs β β gap β β confirm β β write β
β one-by β β check β β loop β β files β
β one β β + warn β β shape β β + test β
ββββββββββββ ββββββββββββ ββββββββββββ ββββββββββββ
β β β
progress bar flags leaky human reviews loop ready
Qx/7 rendered state / missing blueprint box to invoke
verifier / no stop
# Option A β drop into your global Claude skills folder
git clone https://github.com/EricTechPro/loop-maker ~/.claude/skills/loop-maker
# Option B β install into a custom skills directory
LOOP_MAKER_SKILLS_DIR=~/my-project/.claude/skills ./install.sh/loop-maker
That's it. The wizard runs, asks 7 questions, and writes the scaffolded loop under loops/<name>/ in your project.
- Not a runtime.
loop-makerscaffolds loops; it doesn't execute them. Your loop runs as a separate Claude Code skill or cron job. - Not a single-purpose tool. It works for any autonomous loop β content pipelines, monitoring agents, data-sync jobs, outreach sequences β not one niche use case.
- Not a free pass on the human gate. Question 7 is non-skippable. If an action is irreversible, the scaffold will wire in an approval step β no override.
MIT Β© Eric Tech. See LICENSE.
Designed and maintained by Eric Tech.
Further reading: Addy Osmani on agent design patterns; Anthropic's documentation on agentic loops and tool use.