CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage-issue

Use when triaging a GitHub issue - analyzes issue, checks for duplicates, categorizes, and drafts response

Quality

81%

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

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 body is a highly actionable, well-sequenced triage workflow with executable commands, templates, and validation checkpoints, plus valuable repo-specific security guidance. It is efficient and clearly structured, with only minor room to trim prose and split templates into a reference file.

DimensionReasoningScore

Conciseness

The body is dense with actionable tables, commands, and templates and mostly assumes Claude's competence; minor prose in the warmth-coaching and security sections could be trimmed, but the repo-specific guidance (Hetzner CI flakes, sabotage heuristics) genuinely earns its tokens.

4 / 5

Actionability

Copy-paste-ready `gh issue` commands, a classification table mapping indicators to actions, and fill-in response templates cover the common triage cases concretely and executably.

5 / 5

Workflow Clarity

Six steps are clearly sequenced with a graphviz diagram, a classification checklist, confidence rating, and a security-analysis checkpoint providing validation before mutation; minor gaps (no explicit confirm-before-close loop) keep it just below the top anchor.

4 / 5

Progressive Disclosure

Sections are well-organized and one-level-deep repo references (MIGRATION.md, docs/selinux.md, scripts/destroy.sh) are clearly signaled; the inlined response templates are reasonable for a workflow skill though they could be split into a reference file.

4 / 5

Total

17

/

20

Passed

Description

75%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 concrete, trigger-led, and clearly scoped to GitHub issue triage with four named actions and an explicit "Use when" clause. It is solid but not maximal: trigger synonyms and elaborated trigger phrases would push it to the top anchor.

Suggestions

Add natural trigger synonyms (e.g., "bug report", "issue report") so the skill matches more user phrasings.

Expand the "when" clause with concrete triggers (e.g., "Use when the user asks to triage, classify, or find duplicates of a GitHub issue").

Mention the recommend-action/close step in the action list for full coverage of the triage workflow.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions — "analyzes issue", "checks for duplicates", "categorizes", "drafts response" — but omits adjacent actions like recommending an action/closure, leaving minor coverage gaps rather than full comprehensiveness.

4 / 5

Completeness

Both "what" (the four actions) and "when" ("Use when triaging a GitHub issue") are present and explicit, but the trigger clause is concise and could be more elaborated with concrete trigger phrases, fitting the 4 anchor.

4 / 5

Trigger Term Quality

"triaging" and "GitHub issue" are natural phrases a user would say, but common synonyms such as "bug report" or "issue report" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"triaging a GitHub issue" is a clear niche with distinct triggers and low conflict risk, though it sits adjacent to a fix-issue skill, leaving minor overlap risk rather than minimal.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

mysticaltech/terraform-hcloud-kube-hetzner

Path

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