triage-helper

Assistance with triage of unprioritized issues. Use when the user asks for help with triage.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

90%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 body is an exemplary concise, actionable triage procedure with a clear sequence and an explicit feedback checkpoint. Its only gaps are a slightly informal doc reference and the absence of a structured validation/recovery loop for the noted auth edge case.

Suggestions

Convert the docs/Triaging.md reference into a clearly labeled link (e.g. '## Setup — see [docs/Triaging.md](docs/Triaging.md)') to make the one-level reference more clearly signaled.

Add a brief validate-retry note for the auth edge case (e.g. 'if `gh auth status` fails, run `gh auth login` and retry') to give that step a concrete feedback loop.

Optionally present the per-issue suggestions as a short numbered checklist so the decision workflow reads as an explicit checklist for complex cases.

Dimension	Reasoning	Score
Conciseness	The body is a lean bullet list with no padding and no explanation of concepts Claude already knows; every line earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.	5 / 5
Actionability	It gives a concrete repo URL, a per-issue decision checklist with specific behaviors (close, reproduce, label 'waiting for response', note code pointers, suggest priority with reasoning), and a doc pointer; as an instruction-only skill this is fully actionable guidance covering common cases.	5 / 5
Workflow Clarity	There is a clear sequence (find unlabeled issues, present one at a time, give suggestions, wait for feedback, proceed) with an explicit user-feedback checkpoint; it stops short of a 5 because error-recovery around the auth note is guidance rather than a structured validate-fix-retry loop, and there is no checklist for the multi-case decision step.	4 / 5
Progressive Disclosure	The short body is well organized and points to docs/Triaging.md for detail (signaled twice, one level deep); it does not reach 5 because the reference is a bare path rather than a labeled, sectioned link set, and no bundle files exist to confirm richer structure.	4 / 5
	Total	18 / 20 Passed

Description

57%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 clearly identifies its niche and includes an explicit trigger clause, but it is thin on concrete capabilities and natural keyword variations. It reads as a competent but minimal description rather than a comprehensive one.

Suggestions

List 1-2 concrete actions in the description (e.g. 'finds unlabeled open issues, suggests a priority and labels for each') to lift specificity from 2 to 3-4.

Add natural trigger synonyms such as 'issues', 'labels', or 'prioritization' so the trigger term coverage reaches users who phrase the request differently.

Expand the 'when' clause with concrete trigger phrases (e.g. 'Use when the user asks to prioritize, label, or triage open issues') to push completeness toward 5.

Dimension	Reasoning	Score
Specificity	The phrase 'Assistance with triage of unprioritized issues' names the domain but offers no concrete actions, matching the 'names the domain but actions are minimal or generic' anchor; it does not list even 1-2 specific actions required for a 3.	2 / 5
Completeness	Both 'what' (triage of unprioritized issues) and an explicit 'when' ('Use when the user asks for help with triage') are present, matching the anchor where both exist but could be slightly more specific; a 5 would require concrete trigger phrases with more surface area.	4 / 5
Trigger Term Quality	It includes natural terms like 'triage' and 'help with triage', but lacks common variations and synonyms (e.g. 'issues', 'labels', 'prioritization'), so it is only 'some relevant keywords' rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	'Triage of unprioritized issues' is a clear niche with minimal overlap risk against unrelated skills, fitting 'mostly distinct; minor overlap risk with closely related skills'; it is not a fully comprehensive distinctive trigger set for a 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: flutter/flutter-intellij
Path: .gemini/skills/triage/SKILL.md
Commit: 01f1775

Reviewed: about 13 hours 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.