CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codew-release-qa-sweep

Use before claiming Codewhale release work is done: a pointer to docs/RELEASE_CHECKLIST.md for the gates and to cw-dogfood for the manual QA targets.

Quality

75%

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 ./docs/skills/codew-release-qa-sweep/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean pointer skill: excellent token efficiency and a clean overview-plus-references structure with strong evidence-based reporting rules. Its one real gap is actionability — nothing executable lives in the file itself, so the sweep cannot be started without opening the external checklist and dogfood docs.

Suggestions

Inline a minimal quick-start for the first gate (e.g. the actual `scripts/dev-cargo.sh` and `scripts/dev-test.sh` invocations, and how `check-versions.sh` is run) so the sweep can begin without first opening docs/RELEASE_CHECKLIST.md.

Add a short failure-handling step — what to do when a gate or a manual QA scenario fails (stop the sweep, capture the failing output line, file/link an issue) — to close the feedback loop and lift workflow clarity to full strength.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and assumes competence throughout: every line carries operational weight (issue refs #3216/#2211/#3289, script names, reporting artifacts, explicit prohibitions) with zero padding or explanation of concepts Claude already knows — a clear anchor-5 match, not anchor 4, since there is nothing to trim.

5 / 5

Actionability

Guidance is concrete in form — named files (docs/RELEASE_CHECKLIST.md), scripts (scripts/dev-cargo.sh, dev-test.sh, check-versions.sh), specific regression scenarios, and required report contents — but no executable step lives in the file itself; the entire procedure is deferred to external documents not present in the bundle, matching anchor 3 ('missing key details') rather than anchor 4's inline commands with minor gaps.

3 / 5

Workflow Clarity

A clear two-phase sequence (follow the checklist gates from the canonical checkout, then cw-dogfood step 5 manual QA) with explicit validation checkpoints — 'Don't claim "done", "passing" or "merge-ready" without command output' and 'Name what you skipped' — plus an approval gate on release actions. It falls short of anchor 5 because there is no failure-recovery loop (what to do when a gate or QA scenario fails) and the detailed steps live in the referenced docs.

4 / 5

Progressive Disclosure

This is a textbook pointer skill: a clear overview ('This skill owns nothing itself; it points at the two places that do') with well-signaled, one-level-deep references, each labeled with its purpose ([cw-gates](../cw-gates/SKILL.md) for tools, cw-dogfood step 5 for QA targets, [cw-land](../cw-land/SKILL.md) step 3 for credit). All content is appropriately split into the referenced files and navigation is unambiguous — a direct anchor-5 match.

5 / 5

Total

17

/

20

Passed

Description

62%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 well-scoped description with an explicit trigger clause and named artifacts, distinguishable from generic skills. Its main weaknesses are a thin action vocabulary (it says what it points to, not what happens) and sparse trigger-term coverage lacking common synonyms.

Suggestions

Replace the self-referential 'a pointer to' framing with the concrete gate actions, e.g. 'Runs the Codewhale release gates from docs/RELEASE_CHECKLIST.md (cargo build/test via scripts/dev-cargo.sh and dev-test.sh) and the cw-dogfood manual QA scenarios before work is called done.'

Add natural trigger synonyms users would actually say — 'release checklist', 'cut a release', 'ship-ready', 'release sweep' — so the description matches how the request is likely to be phrased.

DimensionReasoningScore

Specificity

The description names the domain ("Codewhale release work") and two concrete artifacts ("docs/RELEASE_CHECKLIST.md for the gates", "cw-dogfood for the manual QA targets") with their roles, but describes no actions beyond being "a pointer" — matching anchor 3 (domain plus 1-2 concrete items) rather than anchor 4, which requires several specific actions.

3 / 5

Completeness

Both parts are explicitly present: the what ("a pointer to docs/RELEASE_CHECKLIST.md for the gates and to cw-dogfood for the manual QA targets") and a concrete when-clause ("Use before claiming Codewhale release work is done"). It sits just below anchor 5 because the 'what' remains meta — it describes pointers rather than the concrete actions the sweep involves.

4 / 5

Trigger Term Quality

Terms like "release", "QA", "gates", and "claiming... done" are natural for this scenario, but coverage is thin — common variations users would say ("ship", "cut a release", "release sweep", "release candidate") are missing, matching anchor 3 rather than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The trigger is tightly scoped to a specific project and a specific moment (claiming release work done), giving a clear niche with minimal generic conflict. Anchor 4 rather than 5 because the description shares trigger space with the closely related skills it points to — a request to 'run the gates' or 'do QA' could plausibly route to cw-gates or cw-dogfood instead.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 possibly missing (scripts/dev-cargo.sh, scripts/dev-test.sh)

Warning

Total

14

/

16

Passed

Repository

Hmbown/Codewhale

Path

docs/skills/codew-release-qa-sweep/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.