the-loop-autonomy
Skill0 starsChanged 3 months agoMITView on GitHub
Bounded authority lifecycle for grants, expiries, kill switch, and permission 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-autoSkill
- the-loop-cloudSkill
- the-loop-controlSkill
- 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
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 run authority must be explicitly checked before every action, authority windows need to be enforced, and recovery must remain …
- 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 Autonomy
Bounded authority lifecycle for grants, expiries, kill switch, and permission boundaries.
Use when
- Use when run authority must be explicitly checked before every action, authority windows need to be enforced, and recovery must remain faithful when grants are revoked or expired.
Inputs
- Active run, objective, track, and authority context.
- Declared track boundaries and budget controls.
- Typed evidence references and required file paths.
Procedure
- Validate active lease, owner, grant, authority evidence, and stop conditions before mutation.
- Classify authority states into active/expired/revoked and compute the permitted next action matrix.
- Attach explicit rationale for every fallback to manual recovery, approval, or wait states.
- Emit one recoverable/one blocked handoff artifact that prevents ambiguous privilege continuation.
- Seal outcomes with deterministic evidence and status transitions, never inventing authority.
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.