- name
Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file owns a behaviour, choosing which tests to run, testing a change without disturbing the OpenRi
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 developing-openrig -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill developing-openrig -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill developing-openrig -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill developing-openrig -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/.claude/skills/developing-openrigFrom the publisher
This skill is a map to the other maps. Each one is incomplete and may be stale: where a map and the code disagree, the code is right, and fixing the map is a welcome contribution.
If you are an agent running inside OpenRig, two different OpenRigs are in play:
rig --version and rig daemon status describe it.git rev-parse HEAD describes it.Restarting the installed daemon does not run your checkout, and stopping it stops the agents running on it, including you. Test your change with the repo's own harnesses, which start a private daemon and tmux server (see "Test it" below), not by restarting the daemon you live in.
If none of these answers your question, search the code before inventing an answer. A missing map is worth an issue.
If your diff touches anything in arteries.md (message delivery, launch and resume, the queue, rig identity, skill
projection, process observation, migrations, restore):
The short version is npm run build, npm run lint, npm test. test-layers.md has the full ladder, including the
stub-agent scenarios, which run the real CLI, daemon, tmux and SQLite with scripted agents and no model cost.
TMUX and daemon variables, so
it won't touch the daemon your session runs on.OpenRig is a coordination layer for a trusted environment: it should help agents and people keep work flowing.
agent-operated-workflows skill, which ships in the
openrig-core plugin (packages/daemon/assets/plugins/openrig-core/skills/agent-operated-workflows/SKILL.md).Fix it in the same pull request, or open an issue. Update a document's last-verified-against-source marker only when
you have actually checked it against that commit.
© 2026 Skills Rack.
---name: developing-openrigdescription: Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file…---# .claude/skills/developing-openrig/SKILL.mdOverview
Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file owns a behaviour, choosing which tests to run, testing a change without disturbing the OpenRig daemon your own session runs on, judging whether a diff touches a high-risk area, or preparing a pull request. Not for operating rigs (openrig-skills) or designing rig topologies.
FAQ
Download .claude/skills/developing-openrig/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.