CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix

Opt-in workflow for fixing one GitHub issue end to end. Invoked only via `/fix <github-issue-url>` (`$fix` in Codex). Reproduces the bug with our own fixtures, implements the root-cause fix, gets clean independent reviews, opens a draft pull request, makes CI green, runs the Big Bonk review loop and marks the PR ready.

Quality

95%

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

100%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 workflow skill body: lean imperative prose, exact commands and templates, explicit validation gates and recovery loops, and a deliberate one-level-deep split with references/rules.md. Nothing explains what Claude already knows, and every rule encodes non-obvious repository-specific discipline.

DimensionReasoningScore

Conciseness

Every line is repo-specific operational guidance Claude could not infer — "The local `main` ref is often stale: squash or diff against `git merge-base HEAD origin/main`", "A queued or in-progress check is not green" — with zero explanation of concepts Claude already knows and no padding. Not 4 because no section could be trimmed without losing operational information.

5 / 5

Actionability

Copy-paste ready throughout: exact commands (`gh pr list --search "<number>"`, `gh run rerun <id> --failed`, `gh api --paginate repos/{owner}/{repo}/pulls/<n>/reviews`, `git patch-id --stable`) and the verbatim Big Bonk trigger comment to post. Not 4 because the common cases are covered with complete, executable instructions including specific thresholds (~1,500 API calls, last ~25 runs, 10 minutes).

5 / 5

Workflow Clarity

Eight numbered phases with explicit validation checkpoints and feedback loops: "once local targeted tests and `vp check` pass", a five-criterion checklist before `gh pr ready`, "Read the logs of each failure and separate code failures from infrastructure flakes", and loop termination "until the latest review on the latest head approves or reports no actionable findings". Not 4 because validation is explicit at every risky stage rather than having minor gaps.

5 / 5

Progressive Disclosure

Clean split of concerns: shared confirm/reproduce/fix/validate/PR rules are delegated to [`references/rules.md`](references/rules.md) with named-section pointers and an explicit exclusion ("Its 'Automated Runs' section doesn't apply here"), while the skill-owned review/CI/Bonk loops stay inline. The single reference is one level deep, well-signaled, and exists in the bundle; not 4 because navigation is section-precise with no organization gaps.

5 / 5

Total

20

/

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 precise, third-person description that enumerates the full end-to-end workflow and states its invocation trigger explicitly. The only weakness is modest synonym coverage of natural trigger terms, which matters little given the skill is command-invoked only.

DimensionReasoningScore

Specificity

Lists seven concrete actions — "Reproduces the bug with our own fixtures, implements the root-cause fix, gets clean independent reviews, opens a draft pull request, makes CI green, runs the Big Bonk review loop and marks the PR ready" — giving comprehensive coverage of the workflow in consistent third-person voice. Not 4 because coverage is complete rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both: what ("Reproduces the bug… implements the root-cause fix… opens a draft pull request, makes CI green…") and when ("Invoked only via `/fix <github-issue-url>` (`$fix` in Codex)") with a concrete trigger phrase. Not 4 because the when-clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Includes natural phrases users would say such as "fixing one GitHub issue", "bug", "pull request", "CI" and the literal "/fix" command. Not 5 because common synonyms like "bug report", "ticket" or "resolve" are absent; not 3 because the terms present are the ones users of this workflow actually say.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — fixing one GitHub issue end to end in this repository — with "Invoked only via `/fix`" plus `disable-model-invocation: true` eliminating mis-trigger risk. Not 4 because no overlap with neighboring skills is identifiable.

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/fix/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.