CtrlK
BlogDocsLog inGet started
Tessl Logo

issue-triage

Queries and triages open GitHub issues that need attention. Helps identify issues needing milestones, labels, or investigation.

59

Quality

67%

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

Quality

Content

68%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 content is highly actionable and well-structured with real bundle scripts, but redundant warning/table repetition and the absence of a validation loop around batch issue edits hold back conciseness and workflow clarity.

Suggestions

Add a validation checkpoint after applying triage decisions (e.g. 'gh issue view <num> --json milestone' to confirm the milestone was set) to lift workflow clarity above the batch-operation cap.

Remove the 'Common Mistakes to Avoid' table or replace it with a link, since it duplicates the inline DON'T/DO guidance and the CRITICAL warnings already scattered through the steps.

Move the 'Label Quick Reference' and 'Milestone Suggestion Logic' tables into a references/ file, keeping SKILL.md a lean overview that links out.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining known concepts, but the 'Common Mistakes to Avoid' table restates the inline DON'T/DO lists and the 🚨 CRITICAL warnings repeat, which is more than minor trimming.

3 / 5

Actionability

Guidance is fully executable — copy-paste pwsh/gh commands with exact flags, a complete parameter table, and script paths that match the real files in scripts/.

5 / 5

Workflow Clarity

The 6-step triage sequence is clearly ordered, but applying milestones/labels via 'gh issue edit'/'gh pr edit' is a batch mutation with no validation/verification feedback loop, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Scripts are referenced clearly at their use points as one-level-deep references with logic correctly split into .ps1 files; minor gaps stem from the inlined label quick-reference and milestone logic that could live in a separate reference.

4 / 5

Total

15

/

20

Passed

Description

66%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, third-person, and distinct, but it omits an explicit 'Use when...' trigger clause, capping completeness. Adding concrete trigger phrases would lift the weakest dimension.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user asks to triage, groom, or prioritize open GitHub issues, or mentions needing milestone/label assignment.'

Add natural synonyms users say ('tickets', 'bug reports', 'groom the backlog') to broaden trigger coverage.

Optionally name the target repository (dotnet/maui) to sharpen distinctiveness and reduce overlap with generic GitHub skills.

DimensionReasoningScore

Specificity

Third-person voice names the domain (open GitHub issues) and several concrete actions — 'Queries and triages', 'identify issues needing milestones, labels, or investigation' — with only minor coverage gaps.

4 / 5

Completeness

It clearly states the 'what' but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural keywords users would say are present ('GitHub issues', 'triages', 'milestones', 'labels', 'investigation'), with only a few synonyms (e.g., 'tickets', 'bug reports') missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (GitHub issue triage with milestones/labels) with distinct triggers, carrying only minor overlap risk with general project-management skills.

4 / 5

Total

15

/

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
dotnet/maui
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.