rig-lifecycle SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
rig-lifecycle 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/rig-lifecycle@git:20261028.7208632Pins git:20261028.7208632 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mvschwarz/openrig
- Path
skills/_canonical/core/rig-lifecycle/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261028.7208632, committed Oct 28, 2026
- First version recorded
- May 12, 2026
- Size
- 6,185 bytes
- Repository stars
- 8,889
- License
- Apache-2.0
Use when reasoning about the rig lifecycle operations family (create / start / stop / resume / restore / snapshot / release / unclaim / destroy), reading or trusting `rig ps` / lifecycle projections after recovery, or designing proof for a lifecycle scenario. Covers the 4 failure modes (auto-restore creates partial rig; projections report healthier than reality; provider auth treated as impl work; resume succeeds for one runtime fails another) plus the restore-honesty rule…
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
# Rig Lifecycle The family of operations that **create, start, stop, resume, restore, snapshot, release, unclaim, and destroy** OpenRig-managed topologies. Includes the user story after reboot: **"bring my work back without turning a clean recovery into a cleanup project."** If lifecycle is brittle, every higher-level primitive inherits that brittleness. Queue, workflow, seat continuity, cross-host operation, and RSI all assume that rigs and seats can be restored into known states. ## Use this when - Operating `rig up / down / restore / resume / snapshot / release / unclaim / destroy` - Reading `rig ps` after a reboot or recovery and deciding what to trust - Designing proof for a lifecycle scenario (clean start / warm resume / host reboot / provider auth loss / partial boot / operator recovery) - Reasoning about restore-outcome semantics (`resumed` / `rebuilt` / `fresh` / `failed` / `attention_required`) - Auditing whether a lifecycle proof is in-process bedrock vs requires real reboot evidence ## Don't use this when - The operation is single-command and deterministic — use `openrig-user` skill for CLI surface …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_d6sybzsswu2bfstk/9e0c994626b5e67d2548ff87658069ad17eca44f61d2baaef988f23f995fe1c3.json
Then /plugin install rig-lifecycle@markdownregistry-d6sybzsswu2bfstk in Claude Code. It installs git:20261028.7208632, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mvschwarz/openrig/rig-lifecycle@sha256:9e0c994626b5e67dThe line at the top of this page pins the label git:20261028.7208632, 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_d6sybzsswu2bfstk)
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/rig-lifecycle 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 rig-lifecycle from somewhere else? Ask it: where did my rig-lifecycle 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 6 versions of this file, between May 12, 2026 and Oct 28, 2026, about one every 34 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.7208632 latest | 2026-10-28 | 7208632 | 6,185 B | A | view · diff |
| git:20260802.4c6d888 | 2026-08-02 | 4c6d888 | 6,129 B | A | view · diff |
| git:20260518.e8c8298 | 2026-05-18 | e8c8298 | 5,917 B | A | view · diff |
| git:20260513.35ac9f2 | 2026-05-13 | 35ac9f2 | 5,844 B | A | view · diff |
| git:20260513.baacfe8 | 2026-05-13 | baacfe8 | 6,328 B | A | view · diff |
| git:20260512.e2f58fb | 2026-05-12 | e2f58fb | 6,488 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/rig-lifecycle/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 (6185 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_d6sybzsswu2bfstk GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/rig-lifecycle GET https://markdownregistry.com/api/v1/blob/9e0c994626b5e67d2548ff87658069ad17eca44f61d2baaef988f23f995fe1c3
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.
More from mvschwarz/openrig
Every file in mvschwarz/openrig