handoff

Use when capturing session state before switching context, ending a session, or manually preserving progress — creates a structured handoff document in docs/handoffs/ so a future session can resume seamlessly

Quality

83%

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

Quality

Content

82%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 highly actionable, well-structured skill body with executable commands and a complete template. Its main weaknesses are mild verbosity in the cross-agent rationale section and the absence of an explicit post-write validation checkpoint.

Suggestions

Add an explicit validation step after Step 4 (e.g., 'Re-read the saved file and confirm every section is filled with no placeholder text or empty bullets') to turn Step 5's summary into a true feedback loop.

Trim the 'Why this works' paragraph and condense the five cross-agent use cases into a shorter list, since the contract concept is self-evident to Claude.

Consider moving the Automatic Compaction Handoff and Cross-Agent Handoff detail into a separate reference file, keeping SKILL.md as a tighter overview that signals one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The bulk is lean — executable commands and a full template earn their tokens — but the Cross-Agent 'Why this works' paragraph and the five-bullet use-case list are mild over-explanation that could be trimmed, placing it just below a 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready guidance: concrete git/ls commands in Step 1 and a complete markdown document template with frontmatter and section headings covering the common case.	5 / 5
Workflow Clarity	A clearly sequenced 5-step process with a confirm/summary checkpoint in Step 5, but lacks an explicit validation step (e.g., verify all sections are filled and no placeholder text remains); not a destructive/batch operation so no hard cap applies.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, When to Use, Quick Reference, Process, Cross-Agent, Pairs With) and self-contained with no bundle files; over 50 lines so the simple-skill 5 does not apply, and the cross-agent/compaction sections could arguably be split out.	4 / 5
	Total	17 / 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, well-structured description that concretely states what it does and when to use it with natural trigger phrases. Its only weakness is slightly limited trigger synonym coverage and minor overlap with related handoff-family skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'capturing session state', 'creates a structured handoff document in docs/handoffs/', 'a future session can resume' — but omits adjacent operations (listing, archiving), so it falls short of comprehensive (5) and clearly above 1-2 actions (3).	4 / 5
Completeness	Explicitly answers both: 'what' ('creates a structured handoff document in docs/handoffs/ so a future session can resume seamlessly') and 'when' via an explicit 'Use when' clause with three concrete trigger scenarios, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural triggers phrases ('switching context', 'ending a session', 'manually preserving progress') users would actually say, but missing common synonyms like 'compaction', 'context window full', or 'save state' that would warrant a 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche (manual session-state capture) with distinct triggers, but minor overlap risk with closely related sibling skills like handoff-resume, compound, and finishing-a-development-branch referenced in the body.	4 / 5
	Total	17 / 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: lucianghinda/superpowers-ruby
Path: skills/handoff/SKILL.md
Commit: 99fac3d

Reviewed: 6 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.