Install any skill in seconds. Free to start, no credit card required.
Get Started Free →untrivial-ai/bug-triage
Triage bugs reported in chat/issues, search for duplicates, file or update GitHub issues with full context, and push fix PRs.
Passed 15 of 21 test cases with the skill, and 8 of 21 without it.
and 7 more in the full report
9 fixed9 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
A bug causes occasional cosmetic alignment issues in the agent-orchestrator CLI terminal output. The reporter suggested tagging it as `p3` or `low-pri`. Which official priority label must be assigned?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns the priority: low label. | Missed | Passed |
The instructions your model reads when the skill loads.
Triage bugs into well-structured GitHub issues on the correct upstream repo.
git pull origin main. Stale code = bad triage.Untrivial-ai/agent-orchestrator), not forks.| Source | How to gather |
|---|---|
| Discord/Slack thread | Read full thread. Extract: reporter name, original description (the thread starter, not whoever tagged you), screenshots, follow-ups |
| GitHub issue | gh issue view <number> --repo <repo> --json body,comments |
| Live observation | Pull live state via observability tools |
Before tracing code, verify the report has enough substance:
Required (ALL): what happened, where (page/command/feature), when (after upgrade? first time?)
Required (2 of 4): OS/shell/runtime, AO version (ao --version), reproducibility (consistent vs intermittent), reproduction steps
If insufficient, ask:
"I'd like to triage this but need more info: (1) What happened? (error/behavior), (2) Where? (page/command), (3) When did it start?, (4) How to reproduce?"
Gather everything yourself before asking the reporter:
# Environment
ao --version && node --version && echo $SHELL && uname -a
cat agent-orchestrator.yaml
cat ~/.agent-orchestrator/running.json
test cases passed, vs 8 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.