retiring-and-inheriting-a-seat SKILL.md skillA
retiring-and-inheriting-a-seat from mvschwarz/openrig is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mvschwarz/openrig/retiring-and-inheriting-a-seat@git:20261110.60a4a63Pins git:20261110.60a4a63 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mvschwarz/openrig
- Path
packages/daemon/assets/plugins/openrig-core/skills/retiring-and-inheriting-a-seat/SKILL.md- Versions recorded
- 8
- Latest version
- git:20261110.60a4a63, committed Nov 10, 2026
- First version recorded
- Aug 27, 2026
- Size
- 14,277 bytes
- Repository stars
- 8,889
- License
- Apache-2.0
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Retiring and Inheriting a Seat 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. ## Use this when - You are a sitting agent near your context threshold (~85%) with a **planned** transition (or a deliberate role change), and want the successor to start clean. - You are priming a fresh successor into an **existing** seat. - You are recording a tenure in the seat's lineage ledger / writing your tombstone. - You are **inheriting** a seat and need the do-not-over-inherit framing. - You want to consult the agent who sat in this seat before you. ## Don't use this when - Unplanned compaction or a crash already happened — that is the backstop path: `session-compaction-and-restore` / `claude-compaction-restore`. - You need the seat-binding **primitive mechanics** (rebuild/fork/fresh, the two-outcome …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7mffi7srb2ae4fvu/4945abbc7114bf268714bcc2f90fb22a86089f1e7df852e306d739d5df0be127.json
Then /plugin install retiring-and-inheriting-a-seat@markdownregistry-7mffi7srb2ae4fvu in Claude Code. It installs git:20261110.60a4a63, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mvschwarz/openrig/retiring-and-inheriting-a-seat@sha256:4945abbc7114bf26The line at the top of this page pins the label git:20261110.60a4a63, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7mffi7srb2ae4fvu)
5 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in mvschwarz/openrig/retiring-and-inheriting-a-seat since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of retiring-and-inheriting-a-seat from somewhere else? Ask it: where did my retiring-and-inheriting-a-seat come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 8 versions of this file, between Aug 27, 2026 and Nov 10, 2026, about one every 11 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261110.60a4a63 latest | 2026-11-10 | 60a4a63 | 14,277 B | A | view · diff |
| git:20261018.32d2828 | 2026-10-18 | 32d2828 | 14,303 B | A | view · diff |
| git:20261008.72087f3 | 2026-10-08 | 72087f3 | 14,097 B | A | view · diff |
| git:20260907.386e515 | 2026-09-07 | 386e515 | 13,791 B | A | view · diff |
| git:20260901.03606ea | 2026-09-01 | 03606ea | 15,857 B | A | view · diff |
| git:20260830.6f36d8d | 2026-08-30 | 6f36d8d | 15,875 B | A | view · diff |
| git:20260830.44ea56a | 2026-08-30 | 44ea56a | 14,406 B | A | view · diff |
| git:20260827.622323d | 2026-08-27 | 622323d | 14,388 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/retiring-and-inheriting-a-seat/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14277 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mvschwarz/openrig · 8,889 stars · license Apache-2.0 · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7mffi7srb2ae4fvu GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/retiring-and-inheriting-a-seat GET https://markdownregistry.com/api/v1/blob/4945abbc7114bf268714bcc2f90fb22a86089f1e7df852e306d739d5df0be127
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.