Name: handoff
Rating: 68.8 (1 reviews)
Author: alirezarezvani

handoff

Compact the current conversation into a handoff document for another agent to pick up. References existing artifacts (PRDs, plans, ADRs, issues, commits, diffs) by path or URL instead of duplicating them. Use when user wants to hand off the conversation to a fresh agent or starts a new session that picks up prior work.

Quality

85%

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

The canonical home for this skill is handoff in alirezarezvani/claude-skills

Quality

Content

78%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 concise, actionable, single-purpose skill body with a clear workflow and good sectioning. Its main weakness is progressive disclosure: the body twice points to references/companion_tooling.md for tooling detail, but no references/ directory or file is bundled, so the pointer is dangling.

Suggestions

Ship the referenced references/companion_tooling.md (or remove the 'See references/companion_tooling.md' pointer and inline the minimal tooling detail) so navigation is not broken.

Add a one-line verification step (e.g., confirm the handoff path is readable and the doc references real artifact paths before finishing) to strengthen the workflow's feedback loop.

Inline a tiny example of the dedup/reference-by-path guidance so the skill stays actionable even if the companion file is absent.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no concept-explanation padding; the only mild overhead (the derived-from blockquote and version footer) still earns its place as attribution.	5 / 5
Actionability	Provides concrete executable guidance ("Save it to a path produced by `mktemp -t handoff-XXXXXX.md` (read the file before you write to it)") and a concrete section list, but the dedup/template mechanics are delegated to a reference rather than spelled out.	4 / 5
Workflow Clarity	The single-task workflow is clearly sequenced (write doc -> save to mktemp path -> suggest skills -> don't duplicate -> tailor) with a checkpoint ("read the file before you write to it"), but no explicit feedback loop is given.	4 / 5
Progressive Disclosure	Sections and headers are well-organized and the reference is signaled one level deep, but the body leans on references/companion_tooling.md for actual tooling detail and that file does not exist, leaving navigation broken.	3 / 5
	Total	16 / 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.

The description is exemplary: it states concrete capabilities, includes natural trigger terms, and explicitly answers both what the skill does and when to use it. It is clearly distinct from other skills.

Dimension	Reasoning	Score
Specificity	"Compact the current conversation into a handoff document" and "References existing artifacts... by path or URL instead of duplicating them" name the domain and multiple concrete actions (compact, reference-not-duplicate) with comprehensive coverage.	5 / 5
Completeness	Clearly answers both what ("Compact the current conversation into a handoff document") and when ("Use when user wants to hand off the conversation to a fresh agent or starts a new session that picks up prior work") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural terms ("hand off the conversation", "handoff document", "fresh agent", "new session that picks up prior work") that users would actually say, though a few synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (conversation handoff/continuation) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 missing	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	13 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/skills-handoff/SKILL.md
Commit: 19392f7

Reviewed: ~8 hours 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.