Or paste this into your agentInstall the contextcapsule-handoff skill from https://github.com/Johnny-Z13/context-capsule using the skills CLI. Then explain how to create and resume a local handoff in this repository. Do not write files yet.
It inspects the repository, separates observed facts from claims, and asks before writing anything.
Create a Context Capsule handoff for this task. Keep it local and show me what will be written first.
03 / RESUME
Open your next agent
The receiving agent checks that the repository still matches before relying on the saved state.
Resume this task from .contextcapsule/latest.json. Check freshness before continuing.
CompatibleObjective, decisions, verification, blockers, and next action are ready.
The handoff stays in your repository by default. No account, API key, or upload is required.Read the skill source →
Capture, hand off, resume
It carries the minimum useful state across tools without pretending that old context is current.
01 / Capture
Inspect the repository
Record the remote, branch, HEAD, working-tree fingerprint, and changed filenames. Never copy source files into the capsule.
02 / Author
Write the handoff
Separate observed verification from reported claims. Name decisions, blockers, and one concrete next action.
03 / Resume
Check freshness first
Classify the capsule as compatible, stale, mismatched, or unverifiable before trusting repo-specific details.
What the author must make clear
Objective
The outcome, not a transcript of the session.
Status
What is complete, partial, unverified, or explicitly out of scope.
Decisions
Choices the next agent must preserve, with enough reason to avoid accidental reversal.
Verification
The command, result, timestamp, and whether it was observed or merely reported.
Blockers
Anything that needs authority, credentials, another person, or external state.
Next action
One bounded step the receiving agent can actually take.
Local first, trust bounded
The default handoff stays in your repository. The helper excludes its own .contextcapsule/ artifacts from freshness checks, records filenames rather than file contents, and rejects common credential patterns. The agent must ask before writing files, changing ignore rules, or uploading a capsule. A hosted capsule is public to anyone with its URL, so sharing is always an explicit choice.
How it works with ProofSlip
They remain separate products with one clean connection: a capsule can point to proof when a handoff claim needs independent checking.
Navigation
Context Capsule
What is the situation, what matters, and what should the next coding agent do?
Evidence
ProofSlip
What did the release environment actually attest, and can the next agent verify it?
Read every instruction, run the bundled Node helper, adapt the format, or self-host the Hono/Postgres service. The hosted API remains available when you deliberately need a short-lived handoff URL for another machine or person.