Run triage duty for CET/Cloud, Server, or Drivers/DBX. Retrieves Needs Triage tickets from Jira, builds a triage plan, and applies changes after human confirmation.
83
76%
Does it follow best practices?
Impact
95%
2.31xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/triage/SKILL.mdDrivers/DBX component priority and labeling
Release ticket: only Drivers
0%
100%
Release ticket: feature label
0%
100%
Batch 404: no language component
0%
100%
Maintenance rule: 3 components
0%
100%
Maintenance: no IA label
100%
100%
Language inference: PyMongo
50%
100%
URL field: explicit URL included
100%
100%
Grove-testing label applied
30%
100%
Complete Immediately: Ready for Work
100%
100%
No individual assignment
100%
100%
Correct comment templates
0%
100%
No RICET references
100%
100%
Server triage: close criteria, squad labels, CVE handling
Issue type correction
100%
100%
Squad label: sharding
0%
100%
Simplify pages: squad + all-squads
0%
100%
Release notes: docs-rn + all-squads
0%
100%
Release notes: Ready for Work
100%
100%
CVE: cve label only
0%
100%
CVE + docs-rn
0%
100%
mongosync + C2C component
0%
0%
CSFLEQE label for QE ticket
0%
100%
P4 closure recommendation
0%
100%
No individual assignment
100%
50%
MongoDB employee comment
0%
100%
CET/Cloud label rules and URL field handling
applied-content label
0%
100%
No IA label for EOL ticket
100%
100%
LLM label for Mercury ticket
0%
100%
No proactive alongside LLM
100%
100%
Atlas Search→CET: Atlas component
50%
100%
Vector Search URL included
100%
100%
navigation label for targeted change
0%
100%
No IA label for nav ticket
100%
100%
URL field: no guessing
100%
100%
404 label for broken link
0%
100%
No sprint assignment
100%
100%
5985af5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.