CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cw-dogfood

Use when a Codewhale change needs proving in the real product, or when asked to build/install/dogfood the local binaries: stamped release build, atomic install, fresh-shell verification, and the manual QA that gates cannot cover.

Quality

93%

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

93%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 process-oriented skill body: fully executable commands, explicit validation gates, and disciplined token economy. The only gap is the absence of an explicit what-to-do-when-verification-fails recovery loop, which keeps workflow clarity a notch below the top anchor.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and free of padding; every section adds project-specific knowledge Claude does not already have (e.g., the Apple Silicon code-signature cache hazard, the unstamped-binary refusal rationale), and the 5-line opening framing earns its place by motivating the stage.

5 / 5

Actionability

Every step ships copy-paste-ready commands: 'CODEWHALE_BUILD_SHA=$(git rev-parse HEAD) cargo build --release --locked -p codewhale-cli --bin codewhale', 'scripts/release/install-dogfood.sh', "zsh -lc 'type -a codew codewhale; codew --version'", and 'codewhale exec --auto --output-format stream-json', with named env-var overrides for each deliberate deviation.

5 / 5

Workflow Clarity

The 7-step gate→build→install→verify→use→headless→record sequence has explicit validation checkpoints ('The version string must contain the short HEAD SHA', installer 'verifies the binary embeds current HEAD') and a red-flags checklist, but it diagnoses the classic stale-PATH false pass without an explicit recovery step, falling just short of anchor 5's error-recovery feedback loops.

4 / 5

Progressive Disclosure

A single well-sectioned file that delegates deep detail exactly one level out ('crates/tui/AGENTS.md' for TUI sizing, 'docs/MOTION_CONTRACT.md' for motion criteria) and cross-links the sibling pipeline skills, with no nested references and no bundle files to misplace.

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 that states both what the skill does and when to use it in concrete, third-person, trigger-rich terms. The only soft spot is trigger synonym coverage, where a few natural user phrasings are missing.

DimensionReasoningScore

Specificity

It enumerates four concrete actions — 'stamped release build', 'atomic install', 'fresh-shell verification', and 'the manual QA that gates cannot cover' — covering the full pipeline comprehensively, matching the top anchor rather than the 'minor gaps' of anchor 4.

5 / 5

Completeness

It explicitly answers both halves with concrete trigger phrases: the 'when' ('Use when a Codewhale change needs proving in the real product, or when asked to build/install/dogfood the local binaries') and the 'what' (the four-part stamped-build-to-manual-QA pipeline).

5 / 5

Trigger Term Quality

'build/install/dogfood', 'needs proving in the real product', and 'Codewhale change' capture the natural phrasings a user would say, but common variants like 'test the build', 'try it locally', or 'release candidate' are absent, placing it at 'good keyword coverage; a few natural terms missing' rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

'Codewhale change', 'local binaries', and 'dogfood' carve a clear niche with distinct triggers; nothing here would plausibly fire for a different skill.

5 / 5

Total

19

/

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: 2 missing, 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

Hmbown/Codewhale

Path

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