CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

issue-triage

Triage a dotnet/machinelearning GitHub issue locally by selecting the best repository label, adding untriaged, identifying the affected ML.NET area, and drafting a useful maintainer comment. Use when asked to triage, classify, label, or respond to an ML.NET issue.

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

86%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 lean, well-structured skill body that gives exact label taxonomy, comment drafting requirements, and a gated write workflow. The main gaps are the absence of error-recovery handling for verification failures and no example comment or list of project areas to anchor the triage output.

Suggestions

Add a fallback branch to the workflow for when verification fails (e.g., issue already closed, wrong repository, or insufficient detail for any label), so the score-5 feedback-loop anchor is met.

Include one short example maintainer comment (bug case) so the drafted comment format is concrete rather than implied by the checklist.

Enumerate or point to where the likely ML.NET project areas live (e.g., a list of area labels) so 'identify the likely project area' is directly executable.

DimensionReasoningScore

Conciseness

Every token earns its place: a compact inputs table, one-line label definitions with selection criteria, and a terse workflow — no explanations of concepts Claude already knows and no padding.

5 / 5

Actionability

Concrete guidance throughout — exact label names with selection criteria and a specific comment checklist ('inputs, expected and actual behavior, target framework, package version, and platform') — but no example maintainer comment and no enumeration of what the 'likely project area' options are.

4 / 5

Workflow Clarity

A clear six-step sequence with real checkpoints ('Verify the issue is open and belongs to dotnet/machinelearning', 'Show the exact labels and comment before any write', approval gate), but there is no error-recovery guidance if step 1 fails (closed issue, wrong repo), which the score-5 anchor requires.

4 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained with no external references needed, and organized into clear Inputs/Labels/Workflow sections, which merits the top score under the simple-skill guideline.

5 / 5

Total

18

/

20

Passed

Description

92%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 specific, complete, and well-scoped: it states four concrete capabilities and an explicit trigger clause pinned to the ML.NET repository. The only weakness is that trigger-term coverage could include a few more natural synonyms such as 'categorize'.

DimensionReasoningScore

Specificity

Names the domain and four concrete actions — 'selecting the best repository label, adding untriaged, identifying the affected ML.NET area, and drafting a useful maintainer comment' — which comprehensively covers the task; not 4 because there are no coverage gaps.

5 / 5

Completeness

Explicitly answers both 'what' (four concrete actions) and 'when' with concrete trigger phrases ('Use when asked to triage, classify, label, or respond to an ML.NET issue'), matching the top anchor; not 4 because the 'when' clause is explicit and specific.

5 / 5

Trigger Term Quality

'Use when asked to triage, classify, label, or respond to an ML.NET issue' provides good natural keyword coverage, but a few common synonyms (e.g., 'categorize', 'assign a label') are missing, placing it between the good-coverage (4) and comprehensive (5) anchors.

4 / 5

Distinctiveness Conflict Risk

Scoped to a single repository ('dotnet/machinelearning') and a single task with distinct triggers ('triage', 'label', 'untriaged'), giving it a clear niche with minimal conflict risk.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dotnet/machinelearning

Path

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