- 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 forming-an-openrig-mental-model -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill forming-an-openrig-mental-model -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill forming-an-openrig-mental-model -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill forming-an-openrig-mental-model -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/forming-an-openrig-mental-modelFrom the publisher
You're new to OpenRig — or returning after time away — and you need to quickly understand what kind of system this is, what your seat is, and what the moves are. This skill is the fast on-ramp.
For depth, read the canonical reference docs the skill points to. This skill's job is to get you oriented — accurate enough to operate, fast enough to be useful — not to replace the canonical docs.
OpenRig is a local control plane for multi-agent coding topologies. You declare a topology of agents in YAML, boot it with one command, and OpenRig manages tmux sessions, harness lifecycles, transcripts, snapshots, and restoration. When the system goes down, OpenRig snapshots; when it comes back, agents resume their conversations.
The product loop:
down (auto-snapshot) → up <rig-name> (auto-restore) → work → repeat
The unit of work is the rig — a topology of agents working together as a single system.
Everything in agent engineering happens at one of four layers. OpenRig operates at Layer 3.
You are an agent at L1 inside an L2 harness, configured by L3 OpenRig. OpenRig manages your harness; the harness wraps the model; the model generates your tokens.
OpenRig is built on three context-engineering pillars. When you're oriented, you should know which pillar you're operating in:
OpenRig manages topology and exposes public context through rig context.
Project-authored sources supply project-specific knowledge; transcripts retain
recorded work. These sources already coexist. Discover the configured library
and selected task context rather than assuming a particular private corpus:
rig context list shows the configured packs, and rig context work-install
lists what the current project declares (intent, context files, skills), so you
read only the pieces a task needs.
The session-name format {pod}-{member}@{rig} is your address. When you
run rig whoami --json, you get back your full topology context: rig name,
pod, member, peers, edges, transcript path. With output.compact enabled,
a large rig's peer list can be a bounded, edge-first selection: peersNote
then says how many are not shown; rig whoami --json --all-peers lists them all.
OpenRig has five rig classes. The class determines authoring discipline, supervision, and lifecycle policy.
You're probably in a project rig or managed-app rig if you're doing substantive work. Knowing your class helps you understand the supervisory expectations on your seat.
Skills are an established cross-runtime standard at
https://agentskills.io/specification. Both Claude Code and Codex build on it.
A skill is a directory containing SKILL.md (uppercase). The SKILL.md has
YAML frontmatter (name, description) and a Markdown body. Optional
sibling directories: references/, scripts/, assets/.
The harness reads frontmatter cheaply at boot — names + descriptions of all available skills. Body content loads only when a skill activates. This is ambient awareness — you know all the skills exist; you only pay token cost when you reach for one.
profile.uses.skills: [...]
determines what skills get projected into your seat's own skill storage
before your harness boots. A Claude seat gets them through OpenRig's
generated plugin, named openrig:<id>; a Codex seat through its skill
catalog. A seat without that storage gets them in the project's
.claude/skills/ or .agents/skills/. This is the structural
composition layer.imports: [shared] to access a
shared skill pool. Built-in agents commonly do this.The product already discovers its installed shared skill pool and serves
packaged context through rig context list/get. Discovery and retrieval do
not prove that every skill was projected into every harness. Inspect the
selected profile and actual runtime directories; do not assume a universal
home/bootstrap installation from this table.
rig up <rig-name> # boot or restore the topology
rig ps --nodes # see what's running
rig whoami --json # know who you are
rig send <session> "msg" # talk to a peer
rig capture <session> # see a peer's terminal
rig transcript <session> # read a peer's history
rig down <rigId> # snapshot and stop every agent; check rig ps first, only when asked
rig up <rig-name> # restore from snapshot
The first command in any new seat is rig whoami --json. It tells you your
rig, pod, member, peers, edges, and transcript path. Treat it as ground
truth — your CLAUDE.md or AGENTS.md startup overlay can be wrong; whoami
is authoritative.
OpenRig has a few load-bearing cultural principles. Internalize these:
If you're booting into a new seat in an OpenRig rig:
rig whoami --json — recover identity. Know your rig, pod, member,
peers (--all-peers when peersNote says some are not shown).guidance/role.md for your specific seat.CULTURE.md if it has one — the team operating
manual.rig skill loadout --seat self shows
your seat's own skills; .claude/skills/ or .agents/skills/ in your
cwd hold the project's. Each skill has a frontmatter description that
tells you when to reach for it.rig ps --nodes and the queue first (who is up,
who holds what). Capture a peer (rig capture <peer-session>) only when
you actually need to see its screen.rig transcript <session> --tail 100 for recent context.rig ask <rig> "<question>" if you need cross-cutting evidence
from the rig's transcripts and chat.You're now oriented enough to start doing useful work.
Permission policy (at setup): OpenRig sets only a minimal usability floor on your harness permissions, then offers recommended policies you opt into (Locked / Standard / Open — or YOLO to bypass). If you're creating or bringing up a rig, that's a choice you make, not something OpenRig decides for you — see openrig-user's "Permission policy — pick one at setup" and the applying-a-permission-policy skill.
For real depth, these are the load-bearing canonical docs:
If you're going to be authoring rigs, use the openrig-architect skill before
touching YAML.
claude-compaction-restore. Different
skill, different scenario.openrig-architect skill for that.openrig-user for that.This skill exists to form your initial mental model of OpenRig as a system. Once oriented, reach for the role-specific or task-specific skills that fit your actual work.
If you read only this skill, can you:
rig whoami --json and interpret the output?If yes — you're oriented. If no — tell your peer or the human; missing context is fixable, but only if surfaced.
© 2026 Skills Rack.
---name: forming-an-openrig-mental-modeldescription: >----# packages/daemon/assets/plugins/openrig-core/skills/forming-an-openrig-mental-model/SKILL.mdFAQ
Download packages/daemon/assets/plugins/openrig-core/skills/forming-an-openrig-mental-model/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.