agentleFS
Sign inStart free
ba0918ba0918/claude-skills/skills/loop-triage/SKILL.md

loop-triage

Skill0 starsChanged 4 months agoLicence not identifiedView on GitHub

The loop hub skill that detects repository problems with sensors (validate_repo / ledger --check / context-audit and others), makes findings idempotent, classifies them for admission, and pushes them automatically into the .agents/artifacts/issues/ready/ queue. Only AUTO_FIX-class findings are enqueued, and it carries a self-modification gate that demotes changes touching loop definition files to the inbox when they hold no fixture. Use when the user says "loop-triage", "loop triage", "run the sensors and file issues", "push the findings into the queue", "the loop hub", or "the self-modification gate". It sits upstream of issue polling (the consuming side) as the supplying side. For this repository only.

9 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • ayeshakhalid13Skill

    loop-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

  • SUDARSHANCHAUDHARISkill

    loop-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

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free