the-loop-control
Skill0 starsChanged 3 months agoMITView on GitHub
Runtime control plane for stop/recover/halt transitions and explicit escalation boundaries.
In this repository30 other files it gives its agents.
- auditSkill
- bootstrap-agent-contextSkill
- buildSkill
- closeSkill
- decision-logSkill
- feature-trackerSkill
- handoffSkill
- health-checkSkill
- idea-to-briefSkill
- live-state-preflightSkill
- portfolio-reviewSkill
- pre-commit-reviewSkill
- resolveSkill
- retrospectiveSkill
- session-summarySkill
- spec-packSkill
- stack-summarySkill
- strategizeSkill
- testSkill
- the-loop-autonomySkill
- the-loop-autoSkill
- the-loop-cloudSkill
- the-loop-doctorSkill
- the-loop-endlessSkill
- the-loop-parallelSkill
- the-loop-setupSkill
- the-loop-skill-creatorSkill
- the-loopSkill
- the-loop-skill-plannerSkill
- the-loop-watchSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use when multiple agents or lifecycle owners need one explicit control path for run progression.
- Distinctive: line 30
Do not continue any run advancement after control-level terminalization unless recovery evidence exists.
- Distinctive: line 40
Stop with a precise error for missing authority, expired lease, namespace mismatch, unsafe proof, private data exposure, unknown …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The Loop Control
Runtime control plane for stop/recover/halt transitions and explicit escalation boundaries.
Use when
- Use when multiple agents or lifecycle owners need one explicit control path for run progression.
Inputs
- Active run, objective, track, and authority context.
- Declared track boundaries and budget controls.
- Typed evidence references and required file paths.
Procedure
- Map every requested control command to a finite-state transition and verified preconditions.
- Validate namespace, run identity, and lease before any control mutation.
- Apply control atomically with failure rollback; if rollback fails, return precise state.
- Do not continue any run advancement after control-level terminalization unless recovery evidence exists.
- Record control provenance and emitted command/result for later audit.
Output contract
- Deterministic status, evidence hash list, and explicit status transitions.
- Typed halt reason with exact next-step obligations when blocked.
Halt conditions
Stop with a precise error for missing authority, expired lease, namespace mismatch, unsafe proof, private data exposure, unknown capability, or unverified behavior claim.
Notes
Core execution does not require network access or the source checkout. Use the bundled fallback behavior when live capabilities are blocked.
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.