CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage

Investigate an Oxc bug report through triagebot-action's reproduce, diagnose, verify, or fix stage using the affected subsystem's compatibility contract and tests.

Quality

80%

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
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 exceptionally lean, dense orchestration skill: every line encodes triagebot-action-specific operational constraints, concrete paths, tools, and structured return fields. The residual gaps are that the referenced stage files and the 'active finish schema' are not resolvable within the bundle, leaving the deepest execution detail unverifiable.

Suggestions

Ship the referenced stage files (reproduce.md, diagnose.md, verify.md, fix.md) alongside SKILL.md, or note where they live, so the one-level-deep references resolve.

Point to where the 'active finish schema' is found (path or URL) so the structured return format is fully executable from the skill alone.

Add one concrete example of a structured return (e.g. the reproduce stage's fields populated) to close the actionability gap.

DimensionReasoningScore

Conciseness

Every sentence carries non-obvious operational detail ("triageDir is `triage/gh-<issue number>`", "Git ignores `triage/`", "Stop after two attempts at the same infrastructure failure"), with zero space spent explaining concepts Claude already knows. This matches the 5 anchor — lean, assumes competence, every token earns its place — rather than the 4 anchor's "minor instances of over-explanation".

5 / 5

Actionability

Concrete, executable guidance dominates: exact paths (".agents/skills/triage/<step>.md"), tools ("Use `rg` for text and file names, and `ast-grep` for structural code searches"), and exact return fields per stage ("return `reproducible`, `skipped`, and `skippedReason`"). It is not 5 because it defers to "the active finish schema" without locating it, and the per-stage execution detail lives in stage files not shown here, leaving minor gaps.

4 / 5

Workflow Clarity

The orchestration sequence is clear with real checkpoints: each stage "must read the existing `report.md`, if any, and write its result there", "Stop after two attempts at the same infrastructure failure and report what is known", and untrusted issue scripts must be inspected "before running anything". Not 5 because the within-stage workflows and result validation (e.g. how a fix is confirmed) are delegated to the referenced stage files rather than given explicit feedback loops in this body.

4 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled one-level-deep references, each labeled with its purpose ([reproduce.md](reproduce.md), [diagnose.md](diagnose.md), [verify.md](verify.md), [fix.md](fix.md)). Not 5 because none of the referenced stage files (nor [.agents/verification.md](../../verification.md)) exist in the skill bundle, so the navigation cannot be verified and the split of content across files is unconfirmed.

4 / 5

Total

17

/

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, distinctive description that clearly communicates what the skill does within the Oxc/triagebot-action niche. Its main weakness is the missing explicit 'when to use' trigger clause and the absence of common synonyms like "issue", which cap completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when triagebot-action supplies a triage step for an Oxc bug report or when asked to triage an Oxc issue."

Include natural synonyms such as "issue" or "GitHub issue" alongside "bug report" to broaden trigger-term coverage.

Briefly state what the reproduce/diagnose/verify/fix stages produce (e.g. a reproduction, a root-cause diagnosis, a verdict) to close the specificity gap.

DimensionReasoningScore

Specificity

"Investigate an Oxc bug report through triagebot-action's reproduce, diagnose, verify, or fix stage using the affected subsystem's compatibility contract and tests" names the domain and four concrete stage actions plus the method (compatibility contract, tests). It falls short of the 5 anchor because it never says what each stage actually does, leaving minor coverage gaps, but lists well more than the 1-2 actions of the 3 anchor.

4 / 5

Completeness

The "what" is clear (investigate an Oxc bug report through the four triage stages), but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines. The "when" is only weakly implied by "an Oxc bug report" existing, which matches the 3 anchor rather than the explicit 'when' of the 4 anchor.

3 / 5

Trigger Term Quality

Natural terms a handler of an Oxc bug would say are present: "bug report", "reproduce", "diagnose", "verify", "fix", "tests". Not 5 because common synonyms and variations like "issue", "GitHub issue", or "regression" are absent; clearly better than the sparse keyword coverage of the 3 anchor.

4 / 5

Distinctiveness Conflict Risk

The description is anchored to a clear niche — "Oxc bug report", "triagebot-action's reproduce, diagnose, verify, or fix stage", "compatibility contract" — with distinct triggers and minimal overlap with any generic skill. This matches the 5 anchor (clear niche with distinct triggers) rather than the 4 anchor, which still admits overlap with closely related 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 possibly missing (diagnose.md, fix.md, reproduce.md, verify.md), 1 suspicious

Warning

Total

15

/

16

Passed

Repository

oxc-project/oxc

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.