CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-issue

First-contact triage for a GitHub issue

64

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

100%

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, actionable triage runbook: concrete commands, a clear comment template, a decision table, and a sequenced workflow with explicit stop conditions. It is concise and well-organized with no redundant explanation.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — it assumes Claude knows what issues and labels are, uses concrete commands and a fill-in template, and avoids padded explanation, matching 'lean and efficient; every token earns its place'.

3 / 3

Actionability

It provides fully executable commands (the `gh issue view … --json` call, the GraphQL query, `gh issue list --search`), a concrete comment template with literal fields, and a decision table — copy-paste ready and specific.

3 / 3

Workflow Clarity

The five-step workflow is clearly sequenced with explicit checkpoints and stop conditions ('if the input cannot be resolved … stop', 'if the issue is not open, stop unless …', and the ordered label/stop checklist in step 5), satisfying the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

This is a self-contained single-file skill with well-organized sections (label policy, output contract, severity guide, workflow) and no nested or external references, so the well-organized-sections criterion for a 3 is met.

3 / 3

Total

12

/

12

Passed

Description

50%

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 identifies a clear niche but is too terse to score highly: it names the domain and one action without enumerating concrete capabilities or providing an explicit trigger clause. It answers 'what' only weakly and omits 'when'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when triaging a newly opened GitHub issue or when the user asks to do first-contact intake on an issue.'

Enumerate the concrete actions the skill performs, e.g. 'classify, choose a route, post a triage comment, and apply auto-triage labels'.

Include natural trigger variations such as 'issue', 'bug report', and 'intake' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('GitHub issue') and one broad action ('triage'), but does not list the concrete sub-actions the skill performs (classify, route, comment, label), matching the 'names domain and some actions' anchor rather than the multi-action level 3.

2 / 3

Completeness

It states what the skill does ('First-contact triage for a GitHub issue') but has no 'Use when…' or equivalent explicit trigger guidance, so completeness is capped at 2 per the guidelines.

2 / 3

Trigger Term Quality

'GitHub issue' and 'triage' are natural terms a user might say, but coverage is thin with no common variations (e.g. 'issue', 'bug report', 'intake'), fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The GitHub-issue-triage niche is somewhat specific, but the terse generic 'triage' framing could overlap with other issue-handling or review skills, matching 'somewhat specific but could still overlap'.

2 / 3

Total

8

/

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