CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-issue

Assess, classify, and route community-filed issues. Takes a specific issue number or processes all open issues with the state:triage-needed label in batch. Validates agent-first gate compliance, attempts diagnosis using relevant skills, and classifies issues for routing into the spike-build pipeline. Trigger keywords - triage issue, triage, assess issue, review incoming issue, triage issues.

77

Quality

96%

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%Weight 40%Scale 1-3

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

A well-engineered triage workflow with concrete commands, a strong batch confirmation gate, and clear sequencing; the only weakness is that everything lives inline in SKILL.md with no progressive disclosure structure.

Suggestions

Move the Step 6 classification table and the Step 7 comment template into a reference file (e.g. references/classification.md) and link to it from SKILL.md, keeping the main body as a lean overview.

Extract the Step 5 sub-agent prompt block into a reference so the core workflow reads as a concise 7-step spine.

Consider a references/ directory entry for the relationship-to-other-skills diagram and routing detail to reduce the inline footprint further.

DimensionReasoningScore

Conciseness

The body is procedural and lean — concrete gh commands, a classification table, and templates rather than explanations of concepts Claude already knows; the only repetition (the agent-ready human-gate) is deliberate safety reinforcement, so it earns its tokens.

3 / 3

Actionability

Provides fully executable commands ('gh issue view <id> --json ...', 'gh issue edit <id> --add-label', 'gh release list --limit 10'), a concrete sub-agent prompt, and copy-ready comment/classification templates.

3 / 3

Workflow Clarity

Seven clearly sequenced steps with explicit checkpoints and stop conditions, plus a batch-mode confirmation gate via AskUserQuestion before mass-commenting — the validation the rubric requires for batch operations is present.

3 / 3

Progressive Disclosure

All content is inline in a single ~200-line file with no references or bundle files; sections are well-organized but the skill exceeds the under-50-line exception, so material like the classification table and comment template could be split out.

2 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A strong, third-person description that names concrete actions, provides natural trigger keywords, answers both what and when, and carves out a clear niche distinct from sibling skills like build-from-issue.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Assess, classify, and route community-filed issues', 'Validates agent-first gate compliance, attempts diagnosis', 'classifies issues for routing into the spike-build pipeline' — matching the level-3 anchor.

3 / 3

Completeness

Clearly answers 'what' (assess/classify/route issues, validate gate, diagnose) and 'when' via explicit trigger keywords, satisfying the level-3 'both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Explicit 'Trigger keywords - triage issue, triage, assess issue, review incoming issue, triage issues' gives good coverage of natural phrases a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'community-filed issues' with a 'state:triage-needed label' and a 'spike-build pipeline' niche, giving a clear distinct trigger unlikely to conflict with other skills.

3 / 3

Total

12

/

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
NVIDIA/OpenShell
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.