Issue triage
Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.
npx -y skills add shinzoxD/knackbox --skill issue-triageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Triage bugs and tickets with severity, repro steps, and next actions. Use whenever the user asks to triage issues, prioritize a backlog of bugs, rewrite a bug report, classify severity, or clean up noisy tickets — even from messy Slack reports.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.1 KB, as published. Nobody here has run it
Issue Triage
Triage creates shared clarity: what is broken, how bad, who owns next, and whether it is even a bug.
Severity heuristic
| Severity | Meaning |
|---|---|
| S0/P0 | Total outage or active data loss/security incident |
| S1/P1 | Major feature broken for many; no practical workaround |
| S2/P2 | Important issue with workaround or limited scope |
| S3/P3 | Minor/cosmetic/polish |
Adjust to the team's labels if provided.
Workflow
- Restate the report in one sentence.
- Classify: bug, tech debt, question, feature, duplicate, invalid.
- Severity + impact (users, revenue, trust).
- Repro steps and expected vs actual.
- Missing info checklist.
- Next action + owner role (not necessarily a named person if unknown).
Output format
## Triage: <short title>
**Type:** bug | …
**Severity:** …
**Impact:** …
**Repro:** …
**Expected / actual:** …
**Workaround:** …
**Missing info:** …
**Next:** …
**Duplicate of:** …
Rules
- Do not inflate severity for squeaky wheels without impact evidence.
- Prefer actionable titles ("Checkout 500 on empty cart") over "broken".
- Separate user error / docs gaps from product defects when clear.
- Batch triage tables when many tickets are provided.
- Never invent repro results; mark needs-verification.
- Security reports: minimize public exploit detail; flag private handling.
Edge cases
- No repro: still triage impact; request artifacts (logs, HAR, versions).
- Flaky CI: type as reliability/tech debt with frequency notes.
- Feature disguised as bug: reclassify politely with acceptance criteria ask.