Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fradser/triage
Moves issues and external PRs through a state machine of triage roles — categorise, verify, grill, and write agent-ready briefs.
Passed 15 of 19 test cases with the skill, and 5 of 19 without it.
and 10 more in the full report
11 fixed6 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Draft a comment to be posted on GitHub issue #44 during triage confirming that the bug was verified on the main branch.
| Checked | Without skill | With skill |
|---|---|---|
| The response starts the posted comment with the blockquote `> *This was generated by AI during triage.*`. | 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.*
Every comment or issue posted to the issue tracker during triage must start with > *This was generated by AI during triage.*. Each issue carries exactly one category role and one state role; if state roles conflict, flag it and ask the maintainer before doing anything else.
.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.
test cases passed, vs 5 / 19 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.