CtrlK
BlogDocsLog inGet started
Tessl Logo

issue-triage

Scan open issues and discussions, deduplicate, prioritize, and propose labels. Provides a clean actionable queue.

60

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 ./starters/issue-triage-opencode/skills/issue-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.

The body is concise and well-organized for a simple single-task skill, but its guidance lacks a concrete output template and the batch triage workflow omits an explicit verification checkpoint. Strengthening those would lift the weaker dimensions.

Suggestions

Add a concrete template/example for the issue-triage-state.md output so the deliverables are unambiguous.

Insert an explicit validation checkpoint in the workflow, e.g. 'Before finalizing, confirm no auto-label/close/comment actions were taken and that every P0/P1 item is in the escalate bucket.'

Give a concrete heuristic for flagging 'possible duplicate of #NNN' (e.g., shared title keywords or linked references) instead of leaving dedup unspecified.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations Claude already knows; every section (Scan Sources, Output, Rules) earns its place, matching the score-3 anchor for lean, efficient content.

3 / 3

Actionability

Guidance names concrete deliverables (top 5 P0-P3 items, proposed labels, needs-human bucket, possible duplicates) and specific escalation triggers, but provides no output template or concrete dedup method, leaving key details incomplete.

2 / 3

Workflow Clarity

A scan-to-output sequence is implied by the sections, but this batch operation over many issues has no explicit validation/verification checkpoint (e.g., confirm no auto-actions taken), capping workflow clarity at 2.

2 / 3

Progressive Disclosure

This is a simple skill under 50 lines with no need for external references, and its sections are well-organized, so progressive disclosure scores 3 per the simple-skills scoring note.

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.

The description is specific and occupies a clear niche, but lacks an explicit 'Use when...' trigger clause, capping completeness, and its keyword coverage is only partial. It is solid but not exemplary.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when triaging a backlog of open issues or discussions, or when the user asks to prioritize or deduplicate issues.'

Expand trigger-term coverage to include natural variations like 'triage', 'issue backlog', 'GitHub issues', and 'label proposals'.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Scan", "deduplicate", "prioritize", and "propose labels" — matching the score-3 anchor of listing several specific actions rather than vague language.

3 / 3

Completeness

Clearly states what the skill does, but provides no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes some natural terms users would say ("issues", "discussions", "labels"), but misses common variations and the word "triage" itself; coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

The issue-triage niche (scanning/deduplicating/prioritizing issues and proposing labels) is clearly distinct and unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
cobusgreyling/loop-engineering
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.