CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage-helper

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/triage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a concise, concrete, well-sequenced triage workflow that appropriately delegates GitHub writes away from the agent. Its main defects are a missing executable command for the core issue-retrieval step and a dangling, poorly-signaled reference to docs/Triaging.md that is not part of the bundle.

Suggestions

Add a concrete command for the retrieval step, e.g., a `gh issue list` invocation with the repo, state, and no-priority-label search, so the core action is copy-paste ready.

Fix the docs/Triaging.md reference: make it a proper markdown link, mention it once instead of twice, and either include the file in the bundle or remove the reference.

Add a brief validation step for edge cases, such as what to do when no unlabeled open issues are found or when authentication fails, before entering the one-at-a-time loop.

DimensionReasoningScore

Conciseness

The body is a lean bullet list with no concept explanations or padding, assuming Claude's competence. The duplicate mention of docs/Triaging.md ("Reference `docs/Triaging.md`" and again "There is additional context on our issue triage process in docs/Triaging.md") is a small redundancy that keeps it below anchor 5.

4 / 5

Actionability

Guidance is concrete for an instruction-only skill: a specific repo URL, an auth fallback, a per-issue suggestion catalog, and one-at-a-time pacing. It falls short of anchor 5 because the core retrieval step ('Find the latest open issues... that don't have a priority label') has no copy-paste command, leaving Claude to construct the query.

4 / 5

Workflow Clarity

The sequence is clear (find issues, most-recently-updated first, present one at a time, give suggestions) with an explicit checkpoint ('wait for user feedback before continuing on to the next issue'). It is not anchor 5 because there is no validation or error-recovery step beyond that wait, e.g., for empty result sets or rate limits.

4 / 5

Progressive Disclosure

The skill is short and single-purpose, but its only external reference, docs/Triaging.md, is plain text rather than a clearly signaled link, is mentioned twice, and does not exist in the skill bundle (no references/ or docs/ directory). That matches anchor 3's 'references present but not clearly signaled' rather than the well-organized 5 the simple-skill exception would otherwise allow.

3 / 5

Total

15

/

20

Passed

Description

53%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 correctly pairs a what with an explicit 'Use when' trigger, but both halves are thin: the capability is a single generic action and the trigger vocabulary is one keyword. Adding concrete actions (find unlabeled issues, propose priority labels) and trigger synonyms would lift specificity, trigger quality, and distinctiveness together.

Suggestions

Replace the generic 'Assistance with triage' with 2-3 concrete actions, e.g., 'Finds open issues without priority labels, suggests a priority and labels with reasoning, and recommends closing stale or outdated issues.'

Broaden the trigger clause with natural variations users would say: 'Use when the user asks for help with triage, prioritizing issues, or cleaning up an issue backlog.'

Mention the GitHub issue-tracker context in the description to reduce overlap with other issue-management skills and improve distinctiveness.

DimensionReasoningScore

Specificity

"Assistance with triage of unprioritized issues" names the domain but the action is generic ('Assistance with...'), with no concrete actions such as finding unlabeled issues, suggesting priorities, or closing stale issues. It does not reach anchor 3, which requires 1-2 concrete actions to be listed.

2 / 5

Completeness

Both parts are present: what ("Assistance with triage of unprioritized issues") and an explicit when ("Use when the user asks for help with triage"). It falls short of anchor 5 because the 'what' is vague and the 'when' offers only a single trigger phrase without concrete variations.

4 / 5

Trigger Term Quality

"triage" is a natural keyword a user would say, but it is essentially the only one, repeated in both the capability and trigger clauses. Common variations like "prioritize issues", "backlog grooming", or "labeling issues" are missing, matching anchor 3 rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

"triage of unprioritized issues" is somewhat specific, but without GitHub or issue-tracker context, "issues" is broad enough to overlap with other issue-management or bug-triage skills. It is a fit for anchor 3 rather than anchor 4, since the overlap risk with closely related skills is more than minor.

3 / 5

Total

12

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.