loop-triage
Skill1 starsChanged 3 months agoMITView on GitHub
Goal: Read CI results, open findings, pending reports, and system alerts; produce a prioritized actionable picture for the OWNEX Work Cycles.
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
- SUDARSHANCHAUDHARI/MyLooptheir own version, first seen Nov 1, 2026
- ayeshakhalid13/LoopEngineering-CrashCoursetheir own version, first seen Oct 15, 2026
- rossinsilico/loop-anythingtheir own version, first seen Oct 11, 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
- ba0918/claude-skills★ 0same name
- rossinsilico/loop-anything★ 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- graftSkill
- ownex-atlasSkill
- ownex-forgeSkill
- ownex-odysseySkill
- ownex-pulseSkill
- ownex-securitySkill
- ownex-vaultSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Goal: Read CI results, open findings, pending reports, and system alerts.
“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 — OWNEX Triage Skill
Goal: Read CI results, open findings, pending reports, and system alerts; produce a prioritized actionable picture for the OWNEX Work Cycles.
Scheduling
- Recommended:
/loop 1d— run once per day for morning triage - Active sprints:
/loop 2h— faster signal during intensive cycles
Inputs
STATE.md— previous loop state- Findings with
status=pendingorstatus=in_review - Reports with
status=draft - System health data (pulse:alert events)
- Recent CI/build failures (if CI available)
Outputs
- Updated
STATE.mdwith:- High Priority: items that need immediate action (critical vulns, expired creds, broken pipelines)
- Watch List: items aging without resolution (reports >48h old, findings >72h old)
- Recent Noise: items correctly ignored this run
- Optional: Event bus publishes
loop:triage:completedwith priority items
Phases
- REPORT — Collect current state from all sources
- DISCOVER — Find new items (pending findings, draft reports)
- TRIAGE — Score and prioritize each item
- CLASSIFY — Assign owner/app based on type
- NOTIFY — Publish results + update STATE.md
Human Handoff Points
- Critical-severity vulnerabilities
- Payout decisions ($ amounts)
- Out-of-scope determinations
- Credential rotation approvals
Failure Modes
| Failure | Mitigation |
| Triage noise on healthy system | Tighten priority thresholds |
| False positives | Log as noise; tune classifier |
| Missed critical items | Add event bus subscriptions for critical paths |
| STATE.md grows unbounded | Prune resolved items every run |
Cost Profile
| Scenario | Tokens/run |
| No-op (nothing new) | ~5k |
| Full triage | ~50k |
| With auto-fix (L2) | ~200k |
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.