handoff

Use when managing a two-session handoff — inspecting, picking up, or reviewing a committed handoff package produced by a session=two scope run. The operator interface over the cross-environment handoff lifecycle (plan in one session, build in another, review back in the first). Trigger with /hyperflow:handoff, "list handoffs", "pick up the handoff", "review the handoff build".

Quality

93%

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

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

An exemplary operator-interface skill: terse, concrete, with well-sequenced workflows containing explicit validation and feedback loops, and clean one-level-deep references to detailed materials. No significant weaknesses identified.

Dimension	Reasoning	Score
Conciseness	Lean and efficient body with no concept padding; every line is functional (paths, STATUS values, invocations, commit formats), assuming Claude's competence throughout.	5 / 5
Actionability	Provides fully executable guidance: exact Skill invocations ('skill: dispatch', 'skill: audit' with concrete args), specific paths, STATUS transitions, and a copy-ready commit message format.	5 / 5
Workflow Clarity	The review subcommand is a clear 5-step sequence with an explicit validation gate (STATUS=built else-message) and a feedback loop (NEEDS_FIX → fix-gate, clean pass → deploy gate); complete subcommand coverage is sequenced.	5 / 5
Progressive Disclosure	The body is a thin overview that points one level deep to clearly signaled references (../hyperflow/session-handoff.md, DOCTRINE.md) for package format and shared rules; content is appropriately split and easy to navigate.	5 / 5
	Total	20 / 20 Passed

Description

87%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 purpose and trigger conditions for a narrow niche. It would reach full marks by enumerating the remaining subcommands and adding a few more synonymous trigger phrasings.

Dimension	Reasoning	Score
Specificity	Names the two-session-handoff domain and several concrete actions ('inspecting, picking up, or reviewing a committed handoff package') plus the plan/build/review lifecycle, but does not enumerate all subcommands (list, status, complete), leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' ('operator interface over the cross-environment handoff lifecycle') and 'when' ('Use when managing a two-session handoff' + 'Trigger with…') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes good natural trigger phrases ('list handoffs', 'pick up the handoff', 'review the handoff build') plus the slash command, though a few synonymous phrasings a user might say are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (two-session, cross-environment hyperflow handoff) with distinct, domain-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 suspicious	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/tons-of-skills-marketplace
Path: plugins/ai-agency/hyperflow/skills/handoff/SKILL.md
Commit: 88dcf65

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