triage

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.

2.07x

Quality

68%

Does it follow best practices?

Impact

79%

2.07x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/triage/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable triage workflow with explicit confirmation checkpoints and good progressive-disclosure design, but it is somewhat verbose in its prose rules and the referenced bundle files are absent from the provided bundle.

Suggestions

Break the long single-paragraph rules (e.g., the Empty/Unactionable Ticket Rule at line 25) into short bulleted conditions to improve scannability and trim tokens.

De-duplicate the Server Downstream Change Summary exception, which is stated in the global rule (line 25) and again in Part 2; state it once and cross-reference.

Include the referenced bundle files (references/*.md, assets/comment-templates.md) alongside SKILL.md so the one-level-deep navigation is verifiable and complete.

Dimension	Reasoning	Score
Conciseness	The body is information-dense procedural rules, tables, and JQL rather than padded concept explanation, but several passages could be tightened — notably the ~600-word single paragraph at line 25 and some repeated meta-commentary (e.g., the Server Downstream Change Summary exception restated in Part 2) — placing it at 'mostly efficient but could be tightened' rather than a 4.	3 / 5
Actionability	Guidance is largely executable and copy-paste ready — exact JQL queries, a full Component-to-Team map, enumerated label definitions, and a ready-to-paste Slack template — with minor gaps where routing requires judgment rather than a deterministic command, so it sits at 4 rather than a fully-deterministic 5.	4 / 5
Workflow Clarity	Steps 0–7 plus Part 5 (B1–B4) form a clear sequence with explicit STOP-and-confirm validation gates and plan-revision feedback loops; because this is a batch/destructive Jira operation, the missing post-write verification that applied changes actually succeeded is a minor validation gap that holds it at 4 rather than 5 (the destructive-cap at 3 does not apply because confirmation and read-before-write validation are present).	4 / 5
Progressive Disclosure	SKILL.md acts as a well-structured overview with clearly signaled one-level-deep references to separate team modules (references/cet-cloud.md, server.md, drivers-dbx.md, backlog-squad-classification.md) and assets/comment-templates.md; it is a 4 rather than 5 because those referenced bundle files are not present in this bundle, so the split cannot be fully verified and navigation is not end-to-end complete.	4 / 5
	Total	15 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and clearly differentiated, naming concrete actions and a well-scoped niche, but it omits any explicit 'Use when...' trigger guidance, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases (e.g., 'Use when running triage duty for CET/Cloud, Server, or Drivers/DBX, or when the user mentions Needs Triage DOCSP tickets').

Broaden trigger-term coverage with synonyms users might say (e.g., 'triage Jira tickets', 'triage duty', 'Needs Triage queue').

Optionally enumerate the key actions (apply labels/components/priority, route to owner or backlog, update status) so the 'what' is fully comprehensive.

Dimension	Reasoning	Score
Specificity	Names the triage domain and several concrete actions — 'Retrieves Needs Triage tickets from Jira, builds a triage plan, and applies changes after human confirmation' — but does not enumerate the full set (labeling, components, routing, status changes), leaving minor gaps consistent with a 4 rather than a 5.	4 / 5
Completeness	There is a clear 'what' (retrieve, plan, apply) but no 'when' / 'Use when...' trigger clause, and the guideline caps completeness at 3 when explicit trigger guidance is missing; it is not a 2 because the 'what' is concrete and multi-part.	3 / 5
Trigger Term Quality	Natural trigger terms a user would actually say are present — 'triage duty', 'Needs Triage tickets', 'Jira' — giving good keyword coverage; a few common variations or synonyms are missing, so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	The description carves a clear niche — 'triage duty for CET/Cloud, Server, or Drivers/DBX' on 'Needs Triage tickets from Jira' — with distinct triggers and minimal overlap with other skills, matching the 5 anchor.	5 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 14 missing	Warning

	Total	14 / 16 Passed

Repository: mongodb/docs
Path: .claude/skills/triage/SKILL.md
Commit: d9cb237

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.