Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asymmetric-al/triage
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Passed 14 of 20 test cases with the skill, and 8 of 20 without it.
and 8 more in the full report
8 fixed7 passed either way5 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
An issue was previously marked as waiting for info from the reporter. The reporter has now posted new details addressing those questions. To which state role does the issue transition next?
| Checked | Without skill | With skill |
|---|---|---|
| Transitions the item back to the needs-triage state role upon reporter reply. | Missed | Passed |
The instructions your model reads when the skill loads.
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, using the same roles, same states, and 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.
Every triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.
These are canonical role names. The actual label strings used in the issue tracker may differ. The mapping should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.
State transitions: an unlabeled issue normally goes to needs-triage first; from there it moves to needs-info, ready-for-agent, ready-for-human, or wontfix. needs-info returns to needs-triage once the reporter replies. The maintainer can override at any time; flag transitions that look unusual and ask before proceeding.
test cases passed, vs 8 / 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.