Loading
Use when creating, refreshing, packaging, inspecting, promoting, or deprecating a named per-seat starting point — Agent Starter manifest authoring, the 6-state lifecycle (captured → named → inspectabl
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 agent-starters -a cursor -y
Use when creating, refreshing, packaging, inspecting, promoting, or deprecating a named per-seat starting point — Agent Starter manifest authoring, the 6-state lifecycle (captured → named → inspectable → used → promoted → deprecated), provenance honesty, and refusal rules. NOT a VM image; a managed starting point composed from agent role + startup context + optional native session source + provenance.
Use when creating, refreshing, packaging, inspecting, promoting, or deprecating a named per-seat starting point — Agent Starter manifest authoring, the 6-state lifecycle (captured → named → inspectable → used → promoted → deprecated), provenance honesty, and refusal rules. NOT a VM image; a managed starting point composed from agent role + startup context + optional native session source + provenance.
A named, reusable per-seat starting point. Composes an agent role, startup context, optional native session source, and provenance into something a user or rig can choose when creating, refreshing, or packaging a seat.
This registry-backed startup context is distinct from the rig agent-image
surface and from a VM image. See the current behavior below before treating
optional session provenance as an executable native session source.
rig expand and starter_ref.A starter is valuable when it is functional — it carries the context the seat needs to do its task well. Functional is the only measure of a good starter. Size is not: a smaller starter is not a better one, and a bigger one is not worse. Whatever it took for the seat to become genuinely capable at its job is the right starter — 80K tokens or 800K.
Capture the seat as it naturally is at a functional, proven point. Don't pad it with context the seat doesn't use, and — just as important — don't strip context out to make it smaller. Size is an outcome of what the seat needed, never a target.
Never compact, summarize, or shrink a seat in order to make or "lean" a starter. There is nothing valuable in "smaller," and compaction is lossy — you would trade away the exact capability the starter exists to preserve. (Compaction is a separate last-resort step for a seat genuinely near its context limit, with its own before/after plan — never part of capturing a starter.)
rig expand operation starts from it.Save one entry as <registry-root>/reviewer-v1.yaml. The resolver selects an
explicit root or OPENRIG_AGENT_STARTER_ROOT; absent those, it checks the home
registry ~/.openrig/agent-starters and a configured fallback.
starter_id: reviewer-v1
role: Review the assigned change against its stated outcome.
context: Read the current task and the source needed to judge it.
The current resolver checks the entry shape and credential boundary, then
delivers this YAML itself as one required guidance_merge startup file on a
fresh start. It does not interpret arbitrary context refs, load a native
conversation from this example, or seal an image. A RigSpec member combining
starter_ref with session_source.mode: fork is currently rejected; use a
separate supported session-source path when native continuity is the outcome.
Member usage:
members:
- id: reviewer
starter_ref:
name: reviewer-v1
When a starter points at a primed session produced from a Composable Priming Pack, record:
| Surface | Test type | Authority |
|---|---|---|
| Registry schema accepts minimal starter | unit | daemon or config-layer prototype |
| Inspect shows provenance and included context | unit / snapshot | daemon or CLI |
Member can use starter_ref | integration | daemon |
| Unsupported runtime or stale source refuses honestly | unit + integration | daemon |
| No secret material copied into starter artifact | grep / fixture | tester |
| Bundle can include or reference starter | package inspection | bundle layer |
session-source-fork — native conversation-source continuity; currently not composable with starter_refspecification-system — declarative starter and member referencesrig-bundles-and-shareable-artifacts — shareable starter packagingcontext-engineering-and-retrieval — richer declarative context assemblyseat-continuity-and-handover — refresh and swap workflows over startersAgent Starters need queryable provenance and honest inspect output before RSI loops can rely on them for seat refresh. A workflow must be able to answer: "what starter did this seat use, what source session or context was included, and is that starter still recommended?"
session-source-fork skill — low-level fork primitive that makes native session-based starters possible