ce-handoff

Create a session handoff for another agent, or resume, find, and read any user-selected continuity source. Use when work or conversation must continue without access to the current session history.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable instruction skill with strong validation checkpoints and executable blocks. Its weaker dimensions are conciseness (over-qualified prose) and progressive disclosure (monolithic single file with no reference splitting).

Suggestions

Tighten the hedging prose: trim boundary-qualification sentences like "deliberately open at their edges" and merge semicolon-joined clauses into direct imperatives to cut tokens without losing the safety rules.

Consider splitting the frontmatter contract and the managed-storage shell block into a referenced reference file (e.g. references/handoff-contract.md) signaled one level deep from the body, so the overview stays lean.

Replace the jargon "continuity source" phrasing in the body with natural user terms (e.g. "the handoff", "the source you picked") where the meaning is unchanged.

Dimension	Reasoning	Score
Conciseness	It avoids explaining concepts Claude already knows, but the prose is heavily over-qualified with hedging and boundary-setting (e.g. "deliberately open at their edges"; long semicolon-joined qualifications) that could be tightened without losing substance.	2 / 3
Actionability	Provides an executable bash block for managed storage, a concrete YAML frontmatter template, a copyable resume-invocation rendering rule, and numbered build steps — copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	Clear sequences (Build 1–5, discovery 1–6) with explicit validation checkpoints (confirm destination contains the handoff, symlink/ownership checks, 64-line/16 KiB frontmatter bound, collision retry) and MUST-stop gates; feedback loops are present for the risky operations.	3 / 3
Progressive Disclosure	The body is a single well-sectioned file with no external bundle files or one-level-deep references; at ~130 lines it exceeds the simple-skill exception, so the monolithic structure keeps it below the split-and-navigate anchor.	2 / 3
	Total	10 / 12 Passed

Description

85%Weight 40%Scale 1-3

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 explicitly states both capabilities and an explicit use-trigger, with concrete actions and a distinct niche. The main weakness is trigger-term naturalness, dragged down by the jargon phrase "continuity source".

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Create a session handoff", "resume, find, and read any... source" — matching the anchor for multiple specific concrete actions rather than just naming a domain.	3 / 3
Completeness	Explicitly answers both what ("Create a session handoff... resume, find, and read") and when ("Use when work or conversation must continue without access to the current session history") with an explicit trigger clause.	3 / 3
Trigger Term Quality	Natural terms like "handoff", "resume", "continue", and "session" appear, but "user-selected continuity source" is jargon a user would not say, and common phrasings ("pick up where I left off", "fresh session") are absent.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (inter-agent session continuity) with distinct triggers around continuing without session history, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: EveryInc/compound-engineering-plugin
Path: skills/ce-handoff/SKILL.md
Commit: a9f6d53

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.