CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cw-gates

Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

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 excellent, execution-focused skill body: every rung is backed by exact commands, the escalation logic is explicit, and verification rules are concrete enough to act on immediately. The only trimmable fat is a small amount of incident history that does not change what to do.

DimensionReasoningScore

Conciseness

Dense, imperative guidance that assumes competence and never explains known concepts, but a couple of motivational/history asides ("This repo has been burned twice by the alternative", "since the v0.9.10 gate incident") could be trimmed, and the version-number reference sits outside any old-patterns section.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — fmt check, dev-test.sh invocations with concrete path/area examples, the RUSTFLAGS check, the complete budget-check list, and the exact clippy flag set — covering the common cases.

5 / 5

Workflow Clarity

The rung 1-5 ladder is a clearly sequenced 'climb only as far as the risk requires' workflow with explicit validation checkpoints (quote the count line, check counts per filter group), a feedback loop for failures (focused rerun before calling a flake, root-cause the failure), and a required output checklist that names what was not run.

5 / 5

Progressive Disclosure

No bundle files exist, and the self-contained body is well-sectioned with clear rung-based navigation; detail is correctly delegated one level deep to clearly signaled repo docs (AGENTS.md, docs/RELEASE_CHECKLIST.md, docs/BUILD_PERFORMANCE.md) and sibling skills rather than duplicated inline.

5 / 5

Total

19

/

20

Passed

Description

78%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 compact, well-structured description with an explicit use-when clause carrying natural trigger phrases and a clearly stated scope. Its main weakness is that the what is expressed as content topics rather than concrete actions, which limits specificity.

Suggestions

Rewrite the 'what' half with action verbs, e.g. 'Run the focused-to-broad verification ladder (fmt, targeted tests, budget checks) and quote real command output before claiming a Codewhale change is done.'

Add one or two natural trigger variants such as 'verify', 'tests pass', or 'ship' to broaden the keyword coverage without adding length.

DimensionReasoningScore

Specificity

Names the domain and three concrete components ("the focused-to-broad verification ladder", "the budget checks CI enforces", "the rules for what counts as a passing test") but frames them as topic nouns rather than executable actions, so coverage reads as partial rather than comprehensive.

3 / 5

Completeness

Explicitly answers both questions: the when is concrete ("Use before claiming any Codewhale change is done, green, or ready to land") and the what is explicitly stated (verification ladder, CI budget checks, passing-test rules).

5 / 5

Trigger Term Quality

"done", "green", "ready to land", and "passing" are natural developer phrases anchored by an explicit "Use before claiming..." clause, though common variants like "verify", "ship", or "tests pass" are missing.

4 / 5

Distinctiveness Conflict Risk

The "Codewhale" qualifier carves out a clear niche and keeps overlap risk low, but the generic trigger words "done" and "green" could still collide with other verification or completion-related skills.

4 / 5

Total

16

/

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: 6 suspicious

Warning

referenced_paths_exist

Referenced path issues: 23 missing

Warning

Total

14

/

16

Passed

Repository

Hmbown/Codewhale

Path

docs/skills/cw-gates/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.