Skip to content

Seat Continuity and Handover

Safely replace an AI agent's occupant in a seat while keeping an honest provenance record

Stars
8,553
Licence
Apache-2.0
Files
4 files

What it does

This skill teaches an AI agent how to swap out the agent occupying a named role (a 'seat') in an OpenRig multi-agent setup, such as rebuilding, forking, or starting a fresh occupant, without changing the seat's stable address. It guides the agent to record two separate outcomes (whether continuity was achieved and whether the binding succeeded), to write a provenance record of who replaced whom, and to avoid unsafe shortcuts like renaming seats or auto-rolling back half-finished handovers.

Great for

  • Developers operating OpenRig multi-agent topologies who replace or rebuild seat occupants
  • Operators auditing how a seat's current occupant came to be
  • Teams designing stable agent identities with traceable lineage

Skip it if

  • Users without an OpenRig daemon and CLI, since the commands it references (rig handover, rig seat status) will not exist
  • Freshly created seats with no occupant to replace, which should use rig launch or rig expand instead (reason: the skill does not apply)
  • Live handovers without owner authorization, because the non-dry-run commands can execute real state changes

Try asking

  • “Rebuild the reviewer seat's occupant from its RECAP.md and LEARNED.md and record the provenance”
  • “Plan a dry-run handover of the lead seat to a forked occupant before executing it”
  • “Explain why the seat's continuityOutcome and seatBindingOutcome disagree after a failed handover”
  • “Decide whether the old occupant should retire, advise, or shadow after a swap”
Step-by-step guide: how to use Seat Continuity and HandoverInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 4 original files, the Apache-2.0 licence and an attribution note.

    seat-continuity-and-handover.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip seat-continuity-and-handover.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip seat-continuity-and-handover.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Run commands with --dry-run first and confirm the named owner has authorized the action before executing a real handover
  • Use rig seat status for read-only checks of the seat's state and provenance after any change
  • Do not treat a help listing or dry-run result as proof that a transition succeeded; verify the returned results

What's inside

  • references/apprentice-evidence-toolkit.md
  • references/apprentice-successor-seat-cutover.md
  • references/orchestrator-role.md
  • SKILL.md

Redistributed unmodified from mvschwarz/openrig under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.