handover-resumelisted

Find, inspect, and continue existing Handover context through MCP or the handover-sh CLI. Use when asked to pick up another agent's work, resume from a handover link or slug, switch models without losing state, retrieve report files, or append the next attributable revision.
44-pixels/handover-mcp · ★ 1 · AI & Automation · score 75

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

# Resume context from Handover Continue the canonical record instead of reconstructing work from a transcript. Requires a configured Handover MCP connection or the `handover-sh` CLI with an authenticated Handover identity. ## Select the interface Prefer Handover MCP tools. Fall back to the `handover` CLI. If neither is configured, direct the user to `https://handover.sh/install?utm_source=agent_skill&utm_medium=workflow&utm_campaign=handover_resume_skill`. ## Verify identity and scope - MCP: call `handover.whoami`. - CLI: run `handover whoami --json`. Confirm the intended account and workspace before searching. An empty result can be correct when the identity lacks access; do not bypass it with a copied URL, author name, or organization parameter. Use only the smallest workspace scope needed for the requested record. Never print, copy into artifacts, or ask the user to paste credentials or tokens. If access is denied, preserve the boundary and report it instead of switching to a broader identity. ## Resolve the canonical record 1. If given a Handover URL, slug, or identifier, open that exact record. 2. Otherwise search distinctive nouns, identifiers, filenames, and decisions with `handover.search` or `handover search "<query>" --json`. 3. When several records match, prefer the active canonical record with the newest relevant revision. Ask before choosing when intent remains ambiguous. 4. Read the current revision, artifacts, thread, and open annotations. 5. Do