continue-loop
Skill3 starsChanged 18 days agoApache-2.0View on GitHub
Gives the task once to a persistent worker, then sends only "continue" each round. Run with /baton:continue-loop "<task>".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- asynkron/asynkron-skillstheir own version, first seen Jul 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- asynkron/asynkron-skills★ 32same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- author-flowSkill
- cleanup-flame-chaseSkill
- cleanup-ralphSkill
- fixed-interruptSkill
- flame-chaseSkill
- flowsSkill
- gen-ideaSkill
- gen-planSkill
- goalSkill
- parallel-chase-prSkill
- parallel-chaseSkill
- protocolSkill
- ralph-loopSkill
- recursive-lean-proverSkill
- rlarSkill
- rlcrSkill
- stateful-ralphSkill
The file
Files
continue-loop
Arguments: $ARGUMENTS
Load the run protocol first (Skill tool → baton:protocol; if that fails, Read ${CLAUDE_PLUGIN_ROOT}/skills/protocol/SKILL.md) and follow it. This file only adds what is specific to continue-loop.
Idea
The simplest long run: state the task once, then keep saying "continue". The worker decides what to do next from its own memory and the repository.
Roles
| Role | subagent_type | Model | Session |
| worker | baton:worker | worker model | persistent, named <run-id>-worker |
Turn prompts
Round 1 (Agent call with name):
BATON continue-loop · turn 1/<max> · role worker · run <run-id>
TASK:
<task, verbatim>
You keep this session. After this turn you will only be told "continue". End every turn with your BATON-REPORT.Round n > 1 (SendMessage to <run-id>-worker), exactly:
continueFallback: if the worker can't be reached, play the worker yourself in this session for the remaining rounds and say so in the log.
Stop
- The budget is used up, or a turn fails (protocol).
- Early stop, unless
--no-early-stop: thestreak:line showsdone x2or more andempty x1or more.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.