CtrlK
BlogDocsLog inGet started
Tessl Logo

triage

Triage GitHub issues by applying type, effort, priority, and area labels. Runs in an isolated context to avoid polluting the main conversation with issue details. Delegates to a specialized triage agent with label validation hooks.

59

Quality

70%

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

Quality

Content

72%Weight 40%Scale 1-3

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

A highly actionable, well-organized body with executable gh commands and a clear process, held back slightly by a verbose output template and the absence of a validation checkpoint in a batch labeling workflow.

Suggestions

Add an explicit validation step for batch labeling, e.g. re-fetch each issue's labels after editing and verify the applied categories, retrying on gh command failure.

Trim the two-table summary template to the essential fields to reduce token cost.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no concept over-explanation, but the two-table summary template and the dynamic context block add tokens that could be tightened.

2 / 3

Actionability

It provides real, executable gh commands (label list, issue view, issue edit --add-label) plus a concrete output template, which is copy-paste ready.

3 / 3

Workflow Clarity

The numbered process is clearly sequenced with good decision logic, but this batch labeling operation has no explicit validation/feedback loop, capping the score at 2.

2 / 3

Progressive Disclosure

No bundle files exist; the single-task skill is well-organized into clear sections (Scope, Process, Rules) with no nested references, which satisfies the simple-skill guidance.

3 / 3

Total

10

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 specific, distinctive description that clearly states what the skill does, but it lacks an explicit "Use when..." trigger clause and omits common term variations a user might say.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to triage, categorize, or label GitHub issues."

Broaden trigger terms to include natural variations like "categorize", "tag", "organize", or "prioritize issues".

DimensionReasoningScore

Specificity

It names the concrete domain ("GitHub issues") and enumerates the four specific label categories applied ("type, effort, priority, and area labels"), matching the multiple-specific-actions anchor.

3 / 3

Completeness

The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Natural terms like "Triage", "GitHub issues", and "labels" are present, but common user variations such as categorize, tag, organize, or prioritize issues are missing.

2 / 3

Distinctiveness Conflict Risk

The GitHub issue triage niche with a specific label taxonomy is clearly distinct and unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
coleam00/Archon
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.