handoff

Write or update a handoff document so the next agent with fresh context can continue this work.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/handoff/SKILL.md

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.

The body is a tight, fully actionable, well-sequenced instruction skill that earns top marks on actionability, workflow clarity, and progressive disclosure. Only minor conciseness trims (a duplicated opening line and one redundant parenthetical) keep it from a perfect score.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids padding; it only loses the top point because the opening line duplicates the description and the parenthetical '(so they're not repeated)' restates what 'What Didn't Work' already conveys.	4 / 5
Actionability	Fully actionable instruction-only guidance: concrete numbered steps, exact required sections (Goal, Current Progress, What Worked, What Didn't Work, Next Steps), exact filename (HANDOFF.md), and exact location (project root) plus a clear final action.	5 / 5
Workflow Clarity	Clear, well-sequenced multi-step process (check existence -> read prior context -> create/update with specified sections -> save -> tell user the path) for a low-risk single-purpose skill; no validation checkpoint is needed since writing a markdown doc is neither destructive nor batch, so the simple-skill exception applies.	5 / 5
Progressive Disclosure	A simple skill under 50 lines with no bundle files and no need for external references; it is well organized into a numbered procedure with clearly labeled sub-items, satisfying the simple-skill exception for a top score.	5 / 5
	Total	19 / 20 Passed

Description

53%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.

The description states a clear purpose and domain but lacks an explicit trigger clause and broad natural-keyword coverage, which caps both completeness and trigger quality at the midpoint. It is concise and distinct enough to avoid most conflicts.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when ending a session that another agent will continue, or when the user asks for a handoff/context handoff.'

Broaden natural trigger terms to include synonyms users actually say: 'handoff', 'context handoff', 'pass off work', 'HANDOFF.md'.

Optionally hint at the document structure (goal, progress, what worked, next steps) to lift specificity beyond 1-2 actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('handoff document') and two concrete actions ('Write or update'), matching the anchor that lists 1-2 concrete actions without comprehensive coverage; it does not enumerate the document's sections or update vs. create nuances.	3 / 5
Completeness	Has a clear 'what' (write/update a handoff document) but no explicit 'Use when...' trigger clause, and per the judging guidelines a missing explicit trigger caps completeness at 3; the 'when' is only weakly implied by purpose phrasing.	3 / 5
Trigger Term Quality	Includes a natural term ('handoff document') plus 'fresh context' and 'continue this work', but lacks common variations or synonyms a user might actually say (e.g. 'handoff', 'context handoff', 'HANDOFF.md').	3 / 5
Distinctiveness Conflict Risk	'Handoff document' is a reasonably distinct niche with low overlap risk, but it is not so specific that it could not be confused with general documentation or note-taking skills, so it sits above the midpoint rather than at a clear-niche 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ykdojo/claude-code-tips
Path: skills/handoff/SKILL.md
Commit: 2da5305

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.