handover-recordlisted

Create and validate a portable Handoff Continuity Record, then optionally publish it through Handover MCP or the handover-sh CLI. Use when asked to structure unfinished work for another human or agent, make an AI handoff machine-readable, validate handoff JSON, move work between models, or preserve exact state without depending on a chat transcript.
44-pixels/handover-mcp · ★ 1 · AI & Automation · score 75

Install: claude install-skill 44-pixels/handover-mcp

# Create a portable handoff record Turn current work into a Handoff Continuity Record that another human or agent can validate and continue without receiving the original conversation. The open format is documented at `https://handover.sh/protocol`. Its canonical JSON Schema is `https://handover.sh/protocol/v1/schema.json`. For a human-readable Markdown workflow and receiver verification checklist, use `https://handover.sh/templates/agent-handoff.md?utm_source=agent_skill&utm_medium=workflow&utm_campaign=agent_handoff_checklist`. ## Choose the outcome 1. Create and validate a local JSON record when the user only needs a portable handoff file. 2. Publish the validated record through Handover MCP when `handover.whoami` is available. 3. Otherwise publish through the `handover` CLI when it is installed. 4. If no Handover runtime is configured, keep the validated local result and direct the user to `https://handover.sh/install?utm_source=agent_skill&utm_medium=workflow&utm_campaign=handover_record_skill`. Do not claim it was published. ## Capture exact state Create one JSON object with these eight required groups: - `objective`: the intended outcome and acceptance criteria; - `state`: what is complete, in progress, blocked, and unverified; - `decisions`: choices already made, with reasons and consequences; - `artifacts`: original files, URLs, queries, outputs, or hashes; - `constraints`: permissions, deadlines, budgets, exclusions, and invariants; - `question