CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-helper

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

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

The content is concise, actionable, and clearly sequenced with a feedback checkpoint, but it references docs/Triaging.md which is not present in the bundle, breaking progressive disclosure.

Suggestions

Either add docs/Triaging.md (or a references/ file) with the triage-process details, or remove the dangling reference and inline the essential setup notes.

Mention the docs/Triaging.md reference only once to avoid redundancy.

DimensionReasoningScore

Conciseness

The body is a lean bulleted workflow with no padding and no explanation of concepts Claude already knows; every line earns its place, with only a minor duplicate mention of docs/Triaging.md.

3 / 3

Actionability

It gives concrete guidance: a specific repo URL, tooling fallbacks (github-mcp-server / gh auth status), and a detailed per-issue suggestion taxonomy with an explicit wait-for-feedback control loop.

3 / 3

Workflow Clarity

The sequence (find unlabeled issues, present one at a time, suggest actions, wait for feedback, continue) is explicit with a clear user-feedback checkpoint, and the read-mostly non-destructive scope fits the rubric's simple-skill allowance.

3 / 3

Progressive Disclosure

The body signals a one-level reference to docs/Triaging.md, but that file does not exist in the bundle (no references/assets/docs directories are present), so the navigation pointer is broken.

2 / 3

Total

11

/

12

Passed

Description

75%

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 concise, uses third person, and provides an explicit trigger covering both what and when, though its action language is generic and its trigger coverage is narrow.

Suggestions

Replace "Assistance with" with concrete verbs, e.g. "Finds unlabeled issues and suggests priorities, labels, and next actions for triage."

Broaden the trigger clause to cover natural variations, e.g. "Use when the user asks for help with triage, prioritizing issues, or reviewing the backlog."

DimensionReasoningScore

Specificity

"Assistance with triage of unprioritized issues" names the domain and target object but uses the generic action "Assistance with" rather than listing concrete actions like finding, labeling, or prioritizing issues.

2 / 3

Completeness

It states what the skill does (triage of unprioritized issues) and includes an explicit "Use when..." trigger clause, answering both what and when.

3 / 3

Trigger Term Quality

"Use when the user asks for help with triage" provides one natural trigger phrase, but lacks common variations such as "prioritize issues" or "review the backlog".

2 / 3

Distinctiveness Conflict Risk

"triage of unprioritized issues" with a "help with triage" trigger is a distinct niche unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
flutter/flutter-intellij
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.