CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

92%

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 tight, highly actionable handoff-writing skill with a clear sequenced workflow, an explicit validation checkpoint, and well-signaled one-level-deep references to sibling skills. The only minor gap is a touch of motivational prose in the intro.

Suggestions

Trim the philosophical opening paragraph to a one-line rationale so every remaining token is operational.

Consider marking the refresh block as a verbatim template (e.g. a fenced block the reader copies whole) to reinforce the copy-paste-ready intent.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the opening paragraph ('an optimistic handoff worse than no handoff') carries motivational prose that could be trimmed.

4 / 5

Actionability

Provides a copy-paste-ready bash refresh block and an explicit ordered fill-in structure (authority line, concrete doc paths, SHAs, named dirty files), giving fully executable guidance.

5 / 5

Workflow Clarity

Six numbered steps are clearly sequenced with an explicit verify-first checkpoint (step 2), done/suspected/blocked separation (step 4), and a checklist-style Output section.

5 / 5

Progressive Disclosure

No bundle files to misorganize; cross-skill references (cw-orient, cw-slice, cw-gates) are one level deep and clearly signaled, and sections are well-organized for easy navigation.

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, specific description that clearly states both capability and trigger conditions with concrete, natural-language phrasing. Its only soft spot is slight reliance on the domain term 'Codewhale' rather than more universal synonyms.

DimensionReasoningScore

Specificity

Names multiple concrete outputs — 'takeover prompt, continuation note, or end-of-session summary' — plus structural requirements ('done/suspected/blocked kept separate'), giving comprehensive coverage of the skill's actions.

5 / 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...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like 'takeover prompt', 'continuation note', 'end-of-session summary', and 'handoff' are present, but 'Codewhale' is domain jargon and a few common user phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Codewhale handoffs for another agent or later session) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
Hmbown/Codewhale
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.