Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/triage
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Passed 15 of 20 test cases with the skill, and 10 of 20 without it.
and 9 more in the full report
8 fixed9 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Issue #64 currently carries both 'needs-info' and 'ready-for-agent' state tags on the issue tracker. What action should be taken first?
| Checked | Without skill | With skill |
|---|---|---|
| Flags the conflicting state labels to the maintainer before taking further action. | Missed | Passed |
| Waits for maintainer clarification before executing state changes. | Missed | Passed |
The instructions your model reads when the skill loads.
Use when this workflow matches the user request: Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Source: mattpocock/skills (MIT).
Move issues on the project issue tracker through a small state machine of triage roles.
If this repo treats external pull requests as a request surface (see the issue-tracker config), triage covers them too: a PR is an issue with attached code — same roles, same states, same machine, with a few deltas marked "for a PR" below. Resolve a bare #42 to an issue or PR per the tracker config.
Every comment or issue posted to the issue tracker during triage must start with this disclaimer:
> *This was generated by AI during triage.*
.out-of-scope/ knowledge base worksTwo category roles:
bug — something is brokenenhancement — new feature or improvementFive state roles:
needs-triage — maintainer needs to evaluateneeds-info — waiting on reporter for more informationready-for-agent — fully specified, ready for an AFK agentready-for-human — needs human implementationwontfix — will not be actionedFor a PR, the same states read against the attached code: ready-for-agent means a brief is attached and an agent should take the next step on the diff; ready-for-human means it's ready for a human to merge.
test cases passed, vs 10 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.