CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage

Opt-in workflow for triaging one GitHub issue without fixing it. Invoked only via `/triage <github-issue-url>` (`$triage` in Codex). Establishes live state, reproduces with our own fixtures, probes real Next.js for parity, classifies the issue, and drafts the issue reply and next action. Hands valid bugs off to the fix step.

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

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

An exemplary skill body: a lean skeleton with exact gh/git commands, explicit safety and confirmation gates, and clean one-level delegation to a well-organized rules file. The only minor improvement would be supplying concrete commands for the duplicate-search step.

DimensionReasoningScore

Conciseness

The body is lean and entirely directive with no explanation of concepts Claude already knows — every line (Input handling, Hard Rules, numbered state-establishment, the confirm gate) earns its place.

5 / 5

Actionability

Core operations are copy-paste ready ('gh issue view --comments', 'gh pr list --search "<number>"', 'git fetch origin main', 'gh api rate_limit'), but a few steps remain high-level hints such as 'search open and closed issues and PRs for the same symptom' without a specific command.

4 / 5

Workflow Clarity

A clear numbered two-phase sequence with explicit validation checkpoints: the stale-checkout guard ('A stale checkout produces "already fixed" mistakes'), the rate-limit check before sweeps, and the confirmation gate before posting, labeling, or closing — destructive actions are validated, so the cap at 3 does not apply.

5 / 5

Progressive Disclosure

The body is a concise overview that delegates all detail through one clearly-signaled, one-level-deep link (references/rules.md) whose scope is enumerated ('safety, the parity check, reproducing, the verdict and the reply'); the referenced file exists and does not chain into further nested skill docs.

5 / 5

Total

19

/

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.

A strong description: concise, concrete, and specific about what the skill does, with explicit invocation guidance and a clear boundary against the companion fix skill. The only minor gap is limited synonym coverage of natural trigger phrases.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Establishes live state, reproduces with our own fixtures, probes real Next.js for parity, classifies the issue, and drafts the issue reply and next action' — with comprehensive coverage of the triage workflow, matching the top anchor.

5 / 5

Completeness

Both 'what' and 'when' are answered explicitly: the what via five concrete actions, and the when via equivalent explicit trigger guidance ('Invoked only via `/triage <github-issue-url>` (`$triage` in Codex)'), so the missing-'Use when' cap does not apply.

5 / 5

Trigger Term Quality

Natural terms users would say are present ('triaging', 'GitHub issue', 'bug', 'fix'), giving good keyword coverage, but a few natural variations (e.g. 'reproduce', 'issue report') are absent, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche is stated ('triaging one GitHub issue without fixing it') and explicitly scoped against the fix step ('Hands valid bugs off to the fix step'), with opt-in-only invocation minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

cloudflare/vinext

Path

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