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.

64

Quality

76%

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

85%

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

The body is highly actionable with a well-sequenced, validated workflow and a clean one-level bundle structure. The main weakness is verbosity from restating warnings and DON'Ts in multiple sections.

Suggestions

Collapse the "Common Mistakes to Avoid" table into the existing CRITICAL/DO/DON'T callouts to remove duplicated guidance and shorten the body.

Trim the per-step "What this does" bullets that merely restate the script SYNOPSIS, keeping only details not derivable from the script itself.

DimensionReasoningScore

Conciseness

Mostly efficient procedural guidance, but ~240 lines with repetition — the "Common Mistakes to Avoid" table restates the earlier CRITICAL/DO/DON'T blocks, and some "What this does" bullets echo the script headers.

2 / 3

Actionability

Copy-paste-ready `pwsh` invocations, exact `gh issue edit` / `gh pr edit` syntax, a full parameter table that matches the script's real parameters, and a concrete markdown presentation template.

3 / 3

Workflow Clarity

A clear 6-step sequence with validation checkpoints — scripts self-verify gh install/auth, an explicit reload loop via `-Skip`, and "only stop when query returns zero issues" — giving a proper feedback loop for a batch operation.

3 / 3

Progressive Disclosure

Bundle scripts exist under scripts/ and are referenced inline at one level of depth (`.github/skills/issue-triage/scripts/…`); sections are well-organized with no nested reference chains.

3 / 3

Total

11

/

12

Passed

Description

67%

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 distinct niche, but it omits an explicit "when to use" trigger clause and its trigger terms are only moderately covered. Adding a "Use when…" sentence would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when triaging dotnet/maui GitHub issues, assigning milestones or labels, or finding issues to investigate."

Broaden natural trigger terms to include phrases users actually say, such as "find issues to triage", "assign a milestone", or "label open issues".

DimensionReasoningScore

Specificity

Lists several concrete actions — "Queries and triages open GitHub issues", "identify issues needing milestones, labels, or investigation" — rather than vague language.

3 / 3

Completeness

Clearly states what the skill does, but there is no explicit "Use when…" clause or equivalent trigger guidance, so "when" is only implied — capping completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes natural terms ("GitHub issues", "triage", "milestones", "labels") but the phrase "that need attention" is soft and common variations a user would say are not exhaustively covered.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (triaging open GitHub issues for milestones/labels) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.