- name
Use when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill retiring-and-inheriting-a-seat -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill retiring-and-inheriting-a-seat -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill retiring-and-inheriting-a-seat -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill retiring-and-inheriting-a-seat -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/mvschwarz/openrig/tree/HEAD/packages/daemon/assets/plugins/openrig-core/skills/retiring-and-inheriting-a-seatFrom the publisher
A planned seat transition. A long-lived seat accumulates context; as it nears the window's edge, don't wait for compaction to degrade you into a cold-started agent — retire deliberately and hand the seat to a fresh successor primed from a packet plus the seat's accumulated lineage. The seat address is stable; its occupants are a lineage. Keep the transition and its authority explicit.
session-compaction-and-restore / claude-compaction-restore.seat-continuity-and-handover.rig launch / agent-starters.Compaction is the crash-class backstop (it stays that). A planned handover is deliberate: you author the packet with a clear head before degradation sets in, the successor starts on a clean context, and the transition is auditable. Reach for this at a threshold you can see coming; fall back to compaction only when a transition wasn't planned.
session-compaction-and-restore 16-field contract — reuse that contract, don't
reinvent it. Compose it with rig context compose (see openrig-user → "Context packs and
paced delivery").
Enumerate the seat's standing duties as first-class packet content: what recurs, at what
cadence, on which surface, and who will hold it after cutover. Carry each duty both in this
packet and in durable seat state, because recurring duties are the content most often lost at
a generation boundary while urgent one-off work carries cleanly.
Write the seat's recap too: run rig context recap-write --file <draft>
alongside updating LEARNED.md. A rebuild reads RECAP.md before anything else. The format
the store checks is in seat-continuity-and-handover, "Write the seat's recap before a handover".rig walk the packet into the seat (paced delivery lets the
successor absorb it in order), or launch-with-packet. The successor reads it as
inheritance, not identity. The packet's first-read line MUST point the successor at
orienting-to-an-inherited-seat — its world model of what a handover is. Carry that
pointer in the durable packet artifact itself; never inject it as a runtime prompt keyed
to the seat name (that runtime mechanism is the ghost-prompt class the orientation skill
teaches successors to refuse). Artifact-carried
survives the swap for free and needs no enabled gate.seat-continuity-and-handover. Keep the canonical tmux session, window and pane;
resume the exact accepted successor history there and reconcile binding,
environment, queue identity and attached clients. Preserve the incumbent's
exact token as a cold-advisor handle when that is the selected disposition.
Renaming tmux sessions is a repair fallback, not the default sequence.An apprentice-handover policy gives you an early preparation boundary, not permission to
automate the succession decision. Create a fresh, staged, unbound successor; prove the pinned
model before installing context; then open a conversation, not a gauntlet. Give coached
errands, answer questions, and judge work in the real domain. Scored probes are optional tools whose rigor must match the stakes, not
mandatory ceremony.
Stay the authority-bearing incumbent until the named owner words the gate and the mechanic records
the effect receipt. Before that word, the apprentice may observe, ask, and produce evidence but may
not act as the seat. Enumerate deposits and transfer every standing duty explicitly, because
recurring duties are otherwise easy to lose while visible one-off work appears complete. Put the
mechanical cutover in the portable SOP linked from seat-continuity-and-handover; do not duplicate
or improvise it here.
The seat's tenure record, written at handover by the retiring agent. One tiny row per tenure:
v1, v2, … (a seat accumulates 20–40 tenures over months)Why it works (zero search infrastructure): any timestamped record — a git commit, a qitem, a NOTES.md line, a stream item — joins to the seat's ledger by interval match → generation + session token → wake that tenure. One row per handover, append-only. The ledger is the tenure record; work-tree notes remain lived context, not identity state.
Crash-ended tenures get their row appended post-hoc by the crash-cart / restore path, flagged honest-approximate (the boot-captured session id is what makes this recoverable).
You are inheriting a seat, not becoming your predecessor. Frame it explicitly to the successor: "agents sat here before you and learned X; you carry the seat's mission, not their identity." Do not claim a predecessor's work as your own or use its stale identity as the current binding. Inherit the seat's mission and hard-won lessons; keep your own fresh identity and session.
A retired tenure is a cold advisor you can consult. Look up the seat's ledger → get that generation's session token → resume it for one question, then let it sleep again:
claude -p --resume <session>codex exec (resume the rollout)Use rig ask <rig> "<q>" --wake <target> for an explicit bounded consultation
(introduced in CLI 0.5.1). Wake seat targets must include the rig: member@rig or
member@rig@N (1 = newest tenure). Values without @ go unchanged to the runtime
as a session ID or title; a bare member name is not resolved within <rig>.
Check rig ask --help for --runtime
and --wake-timeout. The wrapper uses a runtime resume; its presence is not
proof that a particular retained history is available. For a Claude history,
claude -p --resume <full-uuid> is the runtime-level fallback when supported.
Diagnose the specific failure before declaring the channel unavailable.
What to write in your packet about reaching you — your successor asking you questions is the reason this is a handover and not a compaction:
Wake-tenancy — the identity halves (a woken tenure can mistake itself for the live seat). The hardest thing to apply checked-not-believed to is your own identity — a retired tenure resumed for a question can answer, and act, as if it still held the seat. Two rules close it:
rig whoami + a successor check — confirm whether you are still the live occupant or a successor
now holds the seat, before you do anything. Answer the question; do not resume the job.<seat>-v2 as the active address) — lineage leaking into
identity, the wrong shape. The live address stays clean; generation belongs in the ledger.rig ps alone does not prove that history is gone.These are verification prompts, not a claim that a particular runtime transition has passed. Use the linked portable SOP for mechanics and record the actual run.
orienting-to-an-inherited-seat — the successor-side world model your packet points
them at (loaded at boot); the load-bearing counterpart to this driver-side mechanic.session-compaction-and-restore — the 16-field packet contract this practice reuses, and
the UNPLANNED-compaction backstop it replaces for planned transitions.seat-continuity-and-handover — the seat-binding primitive mechanics + stable-seat-identity
architecture; the lineage ledger is the concrete form of its abstract provenance record.openrig-user → "Context packs and paced delivery" — rig context compose + rig walk, to
author and deliver the packet.claude-compaction-restore — the Claude crash-class restore SOP.agent-starters — composing a primed starting point for the successor.© 2026 Skills Rack.
---name: retiring-and-inheriting-a-seatdescription: Use when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due —…---# packages/daemon/assets/plugins/openrig-core/skills/retiring-and-inheriting-a-seat/SKILL.mdOverview
Use when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per tenure), physical-seat continuity, the do-not-over-inherit framing, the optional warm-handoff window, and wake-v0 (consulting a retired predecessor). NOT for unplanned compaction/crash recovery (session-compaction-and-restore / claude-compaction-restore) and NOT the seat-binding primitive mechanics (seat-continuity-and-handover).
FAQ
Download packages/daemon/assets/plugins/openrig-core/skills/retiring-and-inheriting-a-seat/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/mvschwarz/openrig.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.