Handoff resume

Skill Vertiso/memory-claude/vertiso-memory/skills/handoff-resume

The official Vertiso Memory plugin for Claude Code.

Install

npx -y skills add Vertiso/memory-claude --skill handoff-resume

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use at session start when hello reports open handoffs, or when the user runs /handoff-resume — finds open handoffs, claims the chosen one, and reconciles it against current reality before resuming work.

SKILL.md

1.7 KB, 364 tokens by cl100k_base, as published. Nobody here has run it

Handoff Resume

Resume a prior session from a handoff — verifying before operating.

Announce: "Using the handoff-resume skill to pick up a prior session."

When to use

The user runs /handoff-resume.
hello reported open handoffs at session start.

Procedure

Call handoff_resume (the MCP tool, or vmem handoff-resume) with no claim argument — this returns the live set of open handoffs.
Branch on the count:
- 0 — nothing to resume; stop here.
- 1 — carry it forward.
- >1 — interactive pick: present one option per handoff (its scope, the writing agent, a one-line state), pre-flagging any that look stale; let the user choose.
Claim the chosen handoff — call handoff_resume again with claim: <id>. Claiming archives it so a parallel session resuming concurrently cannot re-grab it.
Do the recipient diligence the handoff's slot-6 advisory calls for, before operating. Verify the slot-3 "where it stands" state against current reality. Re-confirm any decision or approval recorded in slot 2. The handoff carries its claims honestly, but the world may have moved.
Present the reconciled picture and the concrete pick-up point to the user.

Why verify

The handoff author distinguished what was done from what was believed, but cannot know what changed since. Verification is the recipient's job — do it before you operate, not after.

Gives 0 of the 12 instructions most agent orchestration skills give in 364 tokens

Counted across 742 of the 995 authors here whose files we hold, read 2026-08-06

run the full test suite after integrating changesin 53 of 742, across 20 files
reference existing artifacts by path or URLin 52 of 742, across 22 files
dispatch one agent per independent problem domainin 50 of 742, across 17 files
verify fixes do not conflictin 45 of 742, across 13 files
include a suggested skills section in the documentin 45 of 742, across 15 files
redact sensitive informationin 41 of 742, across 11 files
save to the temporary directory of the operating systemin 39 of 742, across 9 files
tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
spot check agent changes for systematic errorsin 34 of 742, across 7 files
write a handoff document summarising the current conversationin 31 of 742, across 6 files
assign each agent a specific scopein 23 of 742, across 8 files
provide specific scope and clear goalin 23 of 742, across 5 files

Said here and by no other author read

call handoff_resume without a claim argument
stop if zero open handoffs exist
present options if multiple open handoffs exist
claim the chosen handoff by id
perform recipient diligence before operating
re-confirm decisions or approvals recorded in the handoff

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.