Tooluck logoTooluck
SKILL.md

rig-lifecycle

Agent skill frommvschwarz/openrig

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 (failed resume is FAILED loudly — no auto fresh fallback).

How to install rig-lifecycle

install rig-lifecycle
# install the openrig pack with the skills CLI
npx skills add mvschwarz/openrig

# or add only this skill to Claude Code: copy the folder

skills/_canonical/core/rig-lifecycle/

# into

~/.claude/skills/rig-lifecycle/ (all projects)

.claude/skills/rig-lifecycle/ (one project)

skills/_canonical/core/rig-lifecycle/SKILL.md

Apache-2.0Full file
1# Rig Lifecycle
2
3The family of operations that **create, start, stop, resume, restore,
4snapshot, release, unclaim, and destroy** OpenRig-managed topologies.
5Includes the user story after reboot: **"bring my work back without
6turning a clean recovery into a cleanup project."**
7
8If lifecycle is brittle, every higher-level primitive inherits that
9brittleness. Queue, workflow, seat continuity, cross-host operation,
10and RSI all assume that rigs and seats can be restored into known
11states.
12
13## Use this when
14
15- Operating `rig up / down / restore / resume / snapshot / release / unclaim / destroy`
16- Reading `rig ps` after a reboot or recovery and deciding what to trust
17- Designing proof for a lifecycle scenario (clean start / warm resume / host reboot / provider auth loss / partial boot / operator recovery)
18- Reasoning about restore-outcome semantics (`resumed` / `rebuilt` / `fresh` / `failed` / `attention_required`)
19- Auditing whether a lifecycle proof is in-process bedrock vs requires real reboot evidence
20
21## Don't use this when
22
23- The operation is single-command and deterministic — use `openrig-user` skill for CLI surface
24- The work is operator-level configuration or troubleshooting of OpenRig itself — run `rig context get help`
25- The work is rig spec authoring — use `openrig-architect`
26
27## Failure modes (4)
28…

Excerpt shown under the repository's Apache-2.0 license.

More skills in openrig

Newsletter

Join the Community

Subscribe to our newsletter for the latest news and updates