CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage-issue

Triage a GitHub issue against the current fallow codebase and determine validity, priority, scope, and likely implementation shape. Use when the user asks to triage an issue, assess a bug report, or evaluate an enhancement request.

Quality

92%

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.

The body is an exemplar of token-efficient, project-specific instruction: a clear 7-step triage workflow with an explicit reproduce-before-judging gate, a five-level confidence taxonomy for claims, and strict sourcing rules. The main gaps are executable concreteness — no commands for fetching the issue, building from main, or applying the label — and no explicit branch for reports that cannot be reproduced.

Suggestions

Add copy-paste-ready commands for the mechanical steps: how to fetch the issue and comments (e.g., the GitHub connector invocation or `gh issue view`), and the build command for producing a binary from current `main`.

Make the non-reproducible case an explicit workflow branch (e.g., 'If the report does not reproduce on a main-built binary, state that in the triage with a `direct` confidence note and consider closing as fixed'), turning the implicit hint in step 2 into a validation feedback loop.

Show the exact label-application step (command or connector action) for `type:agent-ux` so the final workflow step is executable rather than descriptive.

DimensionReasoningScore

Conciseness

The 39-line body contains no filler: every line is non-obvious, project-specific instruction — the confidence taxonomy ("direct", "supported", "inferred", "speculative", "unknown"), "Write 'because' only with a source: a `file:line`, a commit, or command output", and "Code does not prove the intent of its author". Nothing explains concepts Claude already knows, so it matches the lean/every-token-earns-its-place anchor rather than the 4 anchor's 'minor instances of over-explanation'.

5 / 5

Actionability

Guidance is concrete and directive — a 7-step workflow ("Reproduce the report on a binary built from current `main`"), named pull-in skills (`rust-review`, `panel-review`, `team-assembly`), and a labeled condition for `type:agent-ux`. It falls short of the 5 anchor because nothing is copy-paste executable: no commands for fetching the issue/comments, building the binary from main, or applying the label; it stays above 3 because the steps are specific directives, not vague or pseudocode-level hints.

4 / 5

Workflow Clarity

A clear numbered 7-step sequence with an explicit verification gate — "Reproduce the report on a binary built from current `main` before you judge it" — plus the confidence-level checklist for claims. It does not reach 5 because there is no explicit error-recovery branch (e.g., what to do when the report cannot be reproduced on main is only implied by "A report against an older release can be fixed already"); it is above 3 because the reproduce-before-judging checkpoint is explicit rather than missing. Triage is not a destructive or batch operation, so no cap applies.

4 / 5

Progressive Disclosure

The skill is a single SKILL.md under 50 lines with no references/, scripts/, or assets/ directories and no external references needed; content is organized into well-labeled blocks (Workflow, confidence levels, sourcing rule, pull-in list, closing rule). Per the rubric's simple-skill guideline this matches the top anchor; the cross-references to other skills (`rust-review` etc.) are peer-skill pointers, not nested bundle references.

5 / 5

Total

18

/

20

Passed

Description

95%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 strong: it states concrete capabilities, includes an explicit 'Use when' clause with natural trigger phrasings covering issue/bug-report/enhancement-request variations, and occupies a clear niche (triage of GitHub issues against the fallow codebase). The only weakness is a minor coverage gap — it does not mention the disposition recommendation (keep/split/narrow/close) or acceptance-criteria output that the body delivers.

DimensionReasoningScore

Specificity

Quotes: "Triage a GitHub issue against the current fallow codebase and determine validity, priority, scope, and likely implementation shape" — several specific actions (triage, determine validity, priority, scope, implementation shape). It stays at 4 rather than 5 because the description omits outputs the body treats as core (recommend keep/split/narrow/close, acceptance criteria), leaving minor gaps in coverage; it is well above 3 since it lists more than 1-2 concrete actions.

4 / 5

Completeness

The first sentence explicitly states what the skill does ("Triage a GitHub issue ... determine validity, priority, scope, and likely implementation shape") and the second gives an explicit when-clause with concrete trigger phrases ("Use when the user asks to triage an issue, assess a bug report, or evaluate an enhancement request"). Both what and when are explicit, matching the 5 anchor; the 4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Quotes: "Use when the user asks to triage an issue, assess a bug report, or evaluate an enhancement request" — three natural user phrasings plus "GitHub issue" in the what-clause. Synonym coverage (issue / bug report / enhancement request) is comprehensive for this domain; file extensions are not applicable, so it fits the top anchor rather than the 'a few natural terms missing' anchor at 4.

5 / 5

Distinctiveness Conflict Risk

Quotes: "Triage a GitHub issue against the current fallow codebase" — the skill is anchored to a specific codebase and a distinct task (issue triage with a disposition recommendation, not bug fixing or code review). Triggers like "triage an issue" and "assess a bug report" are distinct and unlikely to fire for unrelated skills, fitting the clear-niche anchor rather than the minor-overlap anchor at 4.

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

fallow-rs/fallow

Path

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