CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-issue

Triage and classify new issues for the CSC database repository. Use this skill whenever an issue is opened, assigned to you, or needs classification. Trigger on: new issue triage, "classify this issue", "what type of issue is this", labelling requests, issue assignment, data correction reports, data addition requests, bug reports, feature requests, or any time you need to categorise, label, prioritise, or respond to a GitHub issue. Also use when deciding whether an issue can be auto-fixed or needs human intervention.

74

Quality

91%

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

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

A concise, highly actionable triage skill with a clear five-step workflow and ready-made response templates. The only gap is an explicit validation checkpoint to confirm label selection before responding.

Suggestions

Add a brief validation step (e.g., "Confirm the chosen category, entity, severity, and action labels are mutually consistent before posting") between Step 4 and Step 5 to close the workflow_clarity gap.

Consider noting a fallback path when an issue does not clearly match any category row, so the agent has explicit guidance for ambiguous cases.

DimensionReasoningScore

Conciseness

Lean tables and short label lists with no padding or explanation of concepts Claude already knows; every line carries an actionable classification rule or template.

5 / 5

Actionability

Provides concrete label taxonomy, severity criteria, assignment targets (@copilot, @dr5hn), and copy-paste-ready response templates with linked external tools and contribution guidelines.

5 / 5

Workflow Clarity

Five clearly sequenced steps (classify, label, severity, action, respond) but no explicit validation/checkpoint step confirming the chosen labels before posting; the destructive/batch cap does not apply since applying labels and posting comments is reversible and non-batch.

4 / 5

Progressive Disclosure

For a short, self-contained single-purpose skill under 50 lines with no need for external references, the content is well-organized into clear section headers, qualifying for the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

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

A strong, explicit description that clearly states both what the skill does and when to use it, with rich natural trigger phrases. Minor specificity gaps (e.g., it describes the intent more than enumerating every concrete action) keep it just short of perfect on action coverage.

DimensionReasoningScore

Specificity

Names the domain (issue triage for the CSC database repo) and several concrete actions: classify, label, prioritise, and respond to GitHub issues, plus decide auto-fix vs human escalation.

4 / 5

Completeness

Explicitly answers what ("Triage and classify new issues") and when ("Use this skill whenever an issue is opened, assigned to you, or needs classification" plus enumerated trigger phrases), matching the 5-anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say: "classify this issue", "what type of issue is this", labelling requests, bug reports, feature requests, data correction/addition reports, all mapped to a single triage intent.

5 / 5

Distinctiveness Conflict Risk

Clearly scoped to GitHub issue triage for a specific database repo with distinct triggers, though the general triage/labeling framing could marginally overlap with other issue-management skills.

4 / 5

Total

18

/

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
dr5hn/countries-states-cities-database
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.