CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

Quality

78%

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

The canonical home for this skill is triage in mattpocock/skills

SKILL.md
Quality
Evals
Security

Quality

Content

77%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-sequenced instruction skill with strong validation checkpoints and concrete templates throughout. Its main weaknesses are dangling references to bundle files that are absent and a dependency on external skills, plus minor repetition in the PR-delta discussion.

Suggestions

Ship AGENT-BRIEF.md and OUT-OF-SCOPE.md alongside SKILL.md (or inline their essentials), since the apply-outcome steps depend on them and they are missing from the bundle.

Provide a fallback for when the 'grilling' and 'domain-modeling' skills are unavailable, or inline a minimal question-round procedure.

Consolidate the PR-delta guidance into one section (the external-PR filter and state-role readings are each explained twice).

DimensionReasoningScore

Conciseness

Dense, imperative writing with no explanation of concepts Claude already knows. Not 5 because of minor repetition: PR deltas are explained in both the intro and the Roles section, and the external-PR filter is described twice.

4 / 5

Actionability

Concrete, executable guidance — exact role names, state transitions, verbatim disclaimer, a needs-info template, and per-outcome actions. Not 5 because it depends on files not in the bundle (AGENT-BRIEF.md) and external skills ('grilling', 'domain-modeling') with no fallback if they are absent.

4 / 5

Workflow Clarity

Explicitly sequenced (gather → recommend → verify → grill → apply) with validation checkpoints ('Wait for direction', 'Verify the claim... Report what happened: confirmed, failed, or insufficient detail') and confirm-before-act guards on the destructive close step.

5 / 5

Progressive Disclosure

References are clearly signaled and one level deep, but both referenced files (AGENT-BRIEF.md, OUT-OF-SCOPE.md) are missing from the bundle, so the promised detail cannot actually be consulted. The body itself is well organized, keeping this above 2.

3 / 5

Total

16

/

20

Passed

Description

70%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.

A specific, well-differentiated description that names concrete triage actions on a distinct domain, but it omits any 'when to use' trigger guidance, which caps completeness and slightly weakens its usefulness as an invocation signal.

Suggestions

Add a 'Use when...' clause naming the trigger phrases, e.g. 'Use when the maintainer asks to triage issues or external PRs, pick up what needs attention, or move an issue to ready-for-agent.'

Include common synonyms such as 'pull request', 'tickets', 'bug reports', and 'labels' so natural user phrasing matches the description.

Replace or briefly gloss the jargon term 'grill' (e.g. 'interrogate the request with rounds of questions') so the capability reads without external context.

DimensionReasoningScore

Specificity

Lists several concrete actions ('categorise, verify, grill if needed, and write agent-ready briefs') on a named domain. Falls short of 5 because 'state machine of triage roles' is abstract and 'grill' is unexplained jargon.

4 / 5

Completeness

Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, which caps this dimension at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Good coverage of natural terms ('issues', 'external PRs', 'triage', 'agent-ready briefs'), but common variations like 'pull request', 'tickets', 'bug reports', or 'labels' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (triage state machine over issue-tracker roles, agent-ready briefs) that is unlikely to mis-trigger against generic review or issue-management skills.

5 / 5

Total

16

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

tonykay/transcriber

Path

.agents/skills/triage/SKILL.md

Revision

a5b30bf

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill