Package an OpenRig agent arrangement and workflow for reuse by others. Guides bundle creation, inspection before installation, and checks in a clean environment to identify hidden dependencies on local paths, providers, or credentials.
Use when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension boundary, or auditing a bundle for portability. Covers the 4 failure modes that prevent bundles from working anywhere but the operator's machine, and the inspect-before-install discipline.
Review the instructions the agent will receive before you install.
A rig bundle is a packaged, shareable artifact that can instantiate an opinionated OpenRig topology and workflow. It may include:
Shareable artifact is broader than bundle: specs, bundles, skills, workflows, and extensions can all be shared. A bundle is the packaged form for "load this topology and way of working."
rig bundle install <path>)rig bundle inspect <path>)extension-and-user-workspace, not bundles.| Concept | Declares | Example |
|---|---|---|
| Bundle | Rig shape + workflow ("load this topology and way of working") | A Velocity Team bundle |
| Extension | Behavior added to user workspace/runtime | A custom command, view, or dashboard |
Don't confuse them. A bundle is opinionated content; an extension is added behavior. Both can be shareable artifacts, but they're structurally distinct.
rig bundle inspect must show what will be created without side effects.Proof should:
Bundles are how proven lab patterns become reusable product experiences:
local dogfood pattern
→ bundle (with manifest, parameterization, proof expectations)
→ installed by another user on clean OpenRig
→ opinionated workflow shipped without becoming a daemon feature
→ if dependable, graduate parts into core daemon
This is also how OpenRig can ship opinionated workflows without making every workflow a daemon feature.
extension-and-user-workspace skill — sibling primitive for user-owned behavior added to runtime; bundle vs extension boundaryspecification-system skill — rig specs / agent specs / workflow specs that bundles packageagent-starters skill — bundles can include or reference Agent Startersopenrig-user skill — rig bundle create / inspect / install CLI surfaceNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Automate website interactions through a command-line browser tool. Navigate pages, fill forms, extract text, save screenshots or PDFs, reuse login sessions, and compare page states to check the effects of actions or website changes.
Design and maintain applications where OpenRig agents help run the system. Organize instructions, shared state, and artifact checks, then trace unexpected behavior to the code, skill, or schema that needs repair.
Design and run bounded procedures in environments where current conditions are uncertain. The skill separates agent judgment from precise tool actions, verifies each effect, and records checkpoints so interrupted work can resume from observed evidence.
Create reusable starting configurations that combine an agent’s role, startup context, and source history. The skill guides registry entries, checks whether their sources are current, and manages their progression from initial capture to recommendation or retirement.
Guides the design and review of agent startup context, including role files and links to authoritative records. It helps identify stale guidance, missing updates, overloaded startup files, and instructions that lose the purpose of the work.
Configure selected OpenRig command permissions in Claude Code or Codex at the agreed project or user scope. Preserve existing restrictions, verify that settings load and behave as intended, and record additions so they can be removed later.