CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-issue

First-contact triage for a GitHub issue

57

Quality

65%

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

82%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 content is a well-structured, highly actionable triage workflow with concrete commands, a clear output contract, and explicit stop checkpoints. Its main weakness is mild redundancy between the label-policy section and the final workflow step.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence, with concrete commands and a tight template, though the label policy is restated in step 5 and a few passages could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready `gh issue view` and `graphql` commands with exact JSON fields, a search command, a full comment template, and a type-to-route table covering the common cases.

5 / 5

Workflow Clarity

Five numbered steps are clearly sequenced with explicit stop/validation checkpoints (unresolvable input, non-open issue), but there is no validate-fix-retry feedback loop, which the task does not strictly require.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized sections and no nested references; no content clearly belongs in separate files, though at ~120 lines it is more than a pure overview.

4 / 5

Total

17

/

20

Passed

Description

48%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 concise and identifies a clear niche, but it is too terse: it states only a single generic action and omits any 'Use when...' trigger guidance. It reads more as a label than an activating description.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases (e.g. 'Use when first looking at a new GitHub issue, or when the user asks to triage or classify an issue').

Expand the 'what' with 1-2 concrete actions, e.g. 'classify the issue, choose a route, post a triage comment, and apply triage labels'.

Include common user phrasings or synonyms (e.g. 'issue intake', 'classify an issue') to improve trigger term coverage.

DimensionReasoningScore

Specificity

The phrase 'First-contact triage for a GitHub issue' names the domain clearly but offers only a single generic action ('triage') with no breakdown into concrete actions like classifying, labeling, or commenting.

2 / 5

Completeness

It gives a reasonably clear 'what' (triage a GitHub issue) but has no explicit 'when' / 'Use when...' trigger clause, which caps completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

'GitHub issue' is a natural term users say, and 'triage' is relevant, but common variations users might actually voice ('look at this issue', 'what to do with this issue') are missing.

3 / 5

Distinctiveness Conflict Risk

The niche (first-contact triage of a GitHub issue) is fairly distinct with clear triggers, though there is minor overlap risk with related issue-handling skills like investigate-issue.

4 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mastra-ai/mastra
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.