- name
>-
SKILL.md
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-operated-workflows -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill agent-operated-workflows -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill agent-operated-workflows -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill agent-operated-workflows -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/mvschwarz/openrig/tree/HEAD/packages/daemon/assets/plugins/openrig-core/skills/agent-operated-workflowsFrom the publisher
An Agent-Operated Workflow is a bounded procedure whose control loop belongs to an agent. The agent observes, interprets, sequences bounded actions, verifies their effects, adapts, and escalates genuine ambiguity. Deterministic code remains the exact substrate; it does not pretend to understand every state of a brownfield world.
agent-operated-software.Calling a model is not enough. A deterministic program that consults a model still owns its loop.
Use an agent when the happy path is deterministic but the environment is brownfield, variable, partially knowable, or disproportionately expensive to model exhaustively. The judgment is in discovering what is true and choosing the next safe act.
Prefer ordinary code when the state space is closed and code is simpler and more reliable than judgment. A parser, fixed data transformation, or fully enumerated state machine does not become better because an agent drives it.
The runbook guides judgment; tools enforce the invariants that must not be arguable.
An interrupted or timed-out mutation is indeterminate, never failed by assumption and never safe to retry blind. Where a compatibility period is safer, separate reversible preparation from the destructive finalizer. Idempotence is a claim to prove per action, not a label for the whole run.
Expose composable verbs, not an optimistic end-to-end controller. Help is inert. Read and plan modes are explicit. Mutations are narrow and independently readable. A failure should say what was observed, why the tool stopped, what remains unchanged, the safe next choices, and where its evidence lives. Keep checkpoints durable, effects observable, and recovery possible without private developer knowledge.
A capability composition is a reusable recipe; this is the execution architecture that operates capabilities toward an outcome. Promote a proven workflow to the composition shelf only after use.
Public example: load skills/core/openrig-upgrade/SKILL.md with
rig context get for the upgrade runbook. Its adjacent scripts/ directory
contains the bounded inspection, backup, plugin-refresh and migration helpers.
Follow that runbook for the procedure; this skill carries the reusable contract.
© 2026 Skills Rack.
---name: agent-operated-workflowsdescription: >----# packages/daemon/assets/plugins/openrig-core/skills/agent-operated-workflows/SKILL.mdFAQ
Download packages/daemon/assets/plugins/openrig-core/skills/agent-operated-workflows/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/mvschwarz/openrig.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.