loop-triage
Skill0 starsChanged 5 months agoMITView on GitHub
Select one bounded task for an agent loop from visible state, real repo evidence, permission boundaries, and a named proof command.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- Rick1330/ibex-harnesstheir own version, first seen Nov 8, 2026
- AdriDob/OWNEXtheir own version, first seen Nov 1, 2026
- SUDARSHANCHAUDHARI/MyLooptheir own version, first seen Nov 1, 2026
- ayeshakhalid13/LoopEngineering-CrashCoursetheir own version, first seen Oct 15, 2026
- cobusgreyling/loop-engineeringtheir own version, first seen Aug 13, 2026
- ayeshakhalid192007-dev/LoopEngineering-CrashCoursetheir own version, first seen Jul 16, 2026
Used with
Projects with it also use loop-budget, loop-constraints and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ayeshakhalid13Skillloop-budget
Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.
Also in 4 projects that use this
- ayeshakhalid13Skill
loop-constraints
Read loop-constraints.md at the start of every run and enforce every rule. This skill runs BEFORE triage or any action skill. Constraints are binding.
Also in 4 projects that use this
SUDARSHANCHAUDHARISkillloop-verifier
The checker half of a maker/checker loop. Independently reviews a proposed fix before it becomes a PR. Has authority to REJECT. Never makes changes itself.
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- cobusgreyling/loop-engineering★ 12ksame name
- Rick1330/ibex-harness★ 57same name
- aiconnai/agentshield★ 21same name
- ayeshakhalid13/LoopEngineering-CrashCourse★ 16same name
- ayeshakhalid192007-dev/LoopEngineering-CrashCourse★ 15same name
- aiconnai/engram★ 3same name
- SUDARSHANCHAUDHARI/MyLoop★ 2same name
- AdriDob/OWNEX★ 1same name
- ba0918/claude-skills★ 0same 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 repository11 other files it gives its agents.
- loop-anythingSkill
- loop-dog-foodSkill
- loop-proveSkill
- loop-recordSkill
- loop-reviewSkill
- loop-anythingSkill
- loop-dog-foodSkill
- loop-proveSkill
- loop-recordSkill
- loop-reviewSkill
- loop-triageSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill at the start of a loop iteration.
- Very specific: line 19
Read loop-state.md and loop-contract.md.
- Distinctive: line 24
Stop if the task needs destructive action, hidden credentials, or a broader permission boundary than the state board allows.
- Very specific: line 29
Write or update the Active Task section in loop-state.md with:
- Distinctive: line 37
Do not implement until the active task and proof command are clear.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Loop Triage
Use this skill at the start of a loop iteration.
Inputs
loop-state.mdloop-contract.md- Current repository state
- Any explicit human instruction for this run
Process
- Read
loop-state.mdandloop-contract.md. - Inspect the real target named by the state board.
- Identify candidate tasks that fit inside one loop iteration.
- Select exactly one task.
- Name the proof command before implementation starts.
- Stop if the task needs destructive action, hidden credentials, or a broader permission boundary than the state board allows.
Output
Write or update the Active Task section in loop-state.md with:
- task
- reason
- expected files or services
- proof command
- stop condition
Do not implement until the active task and proof command are clear.
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.