CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage-issue

First-contact triage for a GitHub issue

Quality

75%

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 ./.mastracode/skills/triage-issue/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 strong, execution-ready instruction set: concrete gh commands, a complete output template, a comprehensive classification/routing table, and a tightly sequenced workflow with stop conditions and a final checklist. Its only flaws are minor redundancy in the opening scope statements; progressive disclosure is clean since the skill needs no external files and none are dangling.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — exact gh commands with JSON field lists, a fill-in comment template, and a decision table with no padding or explanations of known concepts. It is not a 5 because the opening two paragraphs restate the same scope ('classify the issue, choose the next route, post or update one concise issue comment... and stop' vs 'classify the issue, explain the route, update the issue, and stop') and 'Apply only the labels listed above' repeats the Label policy intro.

4 / 5

Actionability

Guidance is copy-paste ready throughout: exact commands ('gh issue view "$ISSUE" --comments --json ...', a parameterized GraphQL query, 'gh issue list --search ...'), an exact comment shape with enumerations for every field, precise label names, and a type/route/approval table covering all common cases. Not below 5 — nothing is pseudocode or abstract.

5 / 5

Workflow Clarity

Five clearly numbered steps with explicit stop conditions ('if the input cannot be resolved, state what is missing and stop', 'if the issue is not open, stop'), validation checkpoints in the gather phase (issue state, existing discussion, closing PRs, duplicates), duplicate-comment handling, and a literal checklist in step 5. The skill processes a single issue and explicitly forbids closing it, so it is neither destructive nor batch and the validation cap does not apply.

5 / 5

Progressive Disclosure

No bundle files (references/scripts/assets) exist and none are referenced — the only cross-references are to sibling skills, not files — so there are no orphaned or nested references. The single-file instruction set is appropriately sized with clear, well-signaled sections (Label policy, Output contract, Workflow) and easy navigation; nothing that belongs in a separate file is inlined.

5 / 5

Total

19

/

20

Passed

Description

45%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 short, domain-specific, and honest, but it undersells the skill: it names the domain without listing the concrete actions (classify, route, comment, label) and provides no 'Use when...' trigger clause. It reads closer to 'Processes PDF files' than to the strong examples that enumerate capabilities plus firing conditions.

Suggestions

Enumerate the concrete actions, e.g. 'Classifies a GitHub issue, chooses the next route, posts one concise triage comment, and applies triage labels.'

Add an explicit trigger clause with natural phrasing, e.g. 'Use when the user asks to triage, label, classify, or do first-pass intake on a GitHub issue.'

State the boundary with adjacent skills to reduce conflict risk, e.g. '...and stops there; use investigation skills for deeper technical debugging.'

DimensionReasoningScore

Specificity

The description names the domain ("GitHub issue", "triage") but names no concrete actions — classify, comment, label, route are all absent. It matches the anchor 'Names the domain but actions are minimal or generic' ("Processes PDF files") rather than level 3, which requires 1-2 explicitly stated actions.

2 / 5

Completeness

It has a clear 'what' (first-contact triage for a GitHub issue) but no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It cannot score 4 without an explicit 'when'.

3 / 5

Trigger Term Quality

"triage" and "GitHub issue" are natural phrases a user would say, but common variations and synonyms ("label", "classify", "intake", "new issue", "issue queue") are missing. Not level 2 since the present keywords are domain-specific and natural, not generic like "works with files"; not level 4 since coverage lacks synonyms.

3 / 5

Distinctiveness Conflict Risk

"First-contact triage for a GitHub issue" carves a somewhat specific niche, but it does not distinguish itself from adjacent issue-handling skills (e.g., issue investigation or deep analysis referenced in the body), so overlap risk with similar skills remains. Not level 4 because the boundary with those related skills is not drawn in the description itself.

3 / 5

Total

11

/

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

mastra-ai/mastra

Path

.mastracode/skills/triage-issue/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.