CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cw-handoff

Use when writing a Codewhale takeover prompt, continuation note, or end-of-session summary for another agent or a later session: a paste-ready handoff grounded in live state, with done/suspected/blocked kept separate.

Quality

89%

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.

A lean, highly actionable instruction skill: the workflow is clearly sequenced with explicit validation (record backstop, verify-first refresh block) and a don't-checklist, and the structure is clean with only well-signaled one-level-deep references. The sole headroom is demonstrating the paste-ready handoff with a skeleton example.

DimensionReasoningScore

Conciseness

Lean and efficient with no generic-concept explanation; even the opening rationale ('an optimistic handoff worse than no handoff: it converts your guesses into the next session's premises') is project-specific and load-bearing, and directives are terse ('If you did not run it, it is not done.'). Every token earns its place; anchor 4 would require trimmable over-explanation, and none is evident.

5 / 5

Actionability

Provides copy-paste-ready commands (the refresh block with 'git status --short --branch' and './scripts/release/check-versions.sh', 'python3 scripts/check-contributor-credit.py') and exact durable paths ('docs/CACHE.md', 'docs/MOTION_CONTRACT.md', 'crates/tui/AGENTS.md'), but never shows a skeleton or filled example of the paste-ready handoff itself — the final artifact's shape is described in the Output section rather than demonstrated. Mostly executable guidance with a minor gap, matching anchor 4.

4 / 5

Workflow Clarity

Six numbered steps in a clear sequence with explicit checkpoints: a pre-write validation step ('Before writing the handoff, run the record backstop and list anything it shows as owed'), a verify-first refresh block ('Tell them to trust that output over anything below it'), and a Red flags checklist for review. This matches anchor 5's clear sequence with explicit validation and a checklist; anchor 4 would require missing checkpoints, and none are.

5 / 5

Progressive Disclosure

No bundle files exist, and the body is appropriately self-contained: well-organized sections (When to use / Workflow / Red flags / Output) with one-level-deep, clearly signaled links to sibling skills only where needed ([cw-orient](../cw-orient/SKILL.md), [cw-slice](../cw-slice/SKILL.md), [cw-gates](../cw-gates/SKILL.md)). Nothing that belongs in a separate file is inlined; navigation is easy, matching anchor 5.

5 / 5

Total

19

/

20

Passed

Description

83%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: it explicitly states both what the skill produces and when to use it, with concrete natural-language triggers and a clearly bounded niche. The only headroom is broader synonym coverage and enumerating the handoff's components.

DimensionReasoningScore

Specificity

Names several concrete deliverables — 'takeover prompt, continuation note, or end-of-session summary' and 'a paste-ready handoff grounded in live state, with done/suspected/blocked kept separate' — but stops short of enumerating the handoff's actual contents (refresh block, dirty-file caveats, next slices), so coverage has minor gaps rather than being comprehensive. Not 5 because anchor 5 demands comprehensive action coverage; not 3 because it goes well beyond naming a domain with 1-2 actions.

4 / 5

Completeness

Explicitly answers both what ('a paste-ready handoff grounded in live state, with done/suspected/blocked kept separate') and when ('Use when writing a Codewhale takeover prompt, continuation note, or end-of-session summary for another agent or a later session') with concrete trigger phrases, mirroring the anchor-5 example structure. Anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say — 'takeover prompt', 'continuation note', 'end-of-session summary', 'handoff', 'another agent', 'later session' — but misses common variations such as 'hand off my work', 'brief the next agent', or 'summary of current state'. Good coverage with a few natural terms missing, matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

'Codewhale takeover prompt' and the qualifier 'for another agent or a later session' carve a clear niche, but 'end-of-session summary' and 'continuation note' retain minor overlap risk with generic summarization or note-taking skills. Mostly distinct with minor overlap, matching anchor 4; not 5 because the conflict risk is not fully minimal.

4 / 5

Total

17

/

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: 1 missing

Warning

Total

14

/

16

Passed

Repository

Hmbown/Codewhale

Path

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