Define reusable OpenRig agent setups, roles, and workflows in specification files. Review dependencies that prevent use on another host, distinguish specifications from bundles and extensions, and verify both file structure and actual execution.
Use when authoring rig specs, agent specs, workflow specs, startup/context fragments, operating-mode declarations, or designing the user spec library. Covers the 4 failure modes (spec instantiates topology but not workflow/mode; spec depends on local paths and fails on another host; agents modify specs as one-off files instead of preserving reusable intent; validation proves YAML shape but not whether topology can run) and the validation-vs-runtime-realization distinction.
Review the instructions the agent will receive before you install.
The declarative primitive family for OpenRig intent: rig specs, agent specs, workflow specs, startup/context fragments, operating-mode declarations, and the user spec library that stores and reuses them.
Specs are how humans and agents describe repeatable topology and behavior without re-explaining it in chat. They are also shareable artifacts: a user should be able to publish a spec or spec family so another user can instantiate the same rig shape, role structure, or workflow pattern.
Without a dependable spec primitive, OpenRig depends on manual startup prompts and tribal memory. That blocks repeatability, product demos, rig bundles, and autonomous rig construction.
rig-bundles-and-shareable-artifacts.extension-and-user-workspace.Proof should:
Validation alone is insufficient.
| Concept | Declares | Example |
|---|---|---|
| Spec | Topology / role / workflow shape (declarative intent) | rig.yaml, agent.yaml, workflow.yaml |
| Bundle | Spec(s) + supporting fragments packaged for shareable instantiation | A Velocity Team bundle |
| Extension | Runtime behavior added to user workspace | RigX command, custom view |
Don't conflate them. The contract should distinguish spec, bundle, and extension cleanly.
OpenRig already has:
agent.yaml, rig.yaml formats; see openrig-architect skill)workflow_specs table; see workflow-runtime skill)rig bundle / spec / agent / specs ls/show/preview/add/sync/remove/rename)packages/daemon/specs/ + ~/.openrig/specs/ per cli-reference.md)Not yet shipped:
openrig-architect skill — RigSpec / AgentSpec authoring disciplineworkflow-runtime skill — workflow spec authoring + transactional-scribe contractrig-bundles-and-shareable-artifacts skill — bundle is the packaged form of specsextension-and-user-workspace skill — extensions add runtime behavior; specs declare intentopenrig/docs/reference/rig-spec.md (product reference doc) — RigSpec format specificationopenrig/docs/reference/agent-spec.md (product reference doc) — AgentSpec format specificationNo 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.