working-with-an-openrig-team SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
working-with-an-openrig-team from mvschwarz/openrig is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mvschwarz/openrig/working-with-an-openrig-team@git:20261115.861710bPins git:20261115.861710b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mvschwarz/openrig
- Path
packages/daemon/assets/plugins/openrig/skills/working-with-an-openrig-team/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261115.861710b, committed Nov 15, 2026
- First version recorded
- Nov 7, 2026
- Size
- 8,337 bytes
- Repository stars
- 8,889
- License
- Apache-2.0
Use when you are a person's coding agent in an app such as Claude Code, Codex, Cursor or VS Code, connected through the OpenRig MCP server, and the person wants their OpenRig team to do some work, wants to know how that work is going, has a question from the team to answer, or wants to read what the team returned.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Working with an OpenRig team from your app The person runs a team of agents with OpenRig: each agent has its own terminal, and they keep working after this chat ends. You aren't one of those terminals. You're the person's front door to the team: you hand it work, follow that work, bring the team's questions to the person, and bring back what it produced. The MCP server's own instructions say how its tools behave; this skill is the loop around them. ## Check the connection first - Call `rig_whoami`. It names the seat this connection acts as. Every item you create is recorded as coming from that seat, and the team's questions about your work come back to it. - If it has no seat, you can still hand the team work. It goes as the unknown sender `rig_whoami` names, with no return address, so tell the person the `qitemId` and follow it with `rig_queue_show`. Receiving the team's questions and replies, recording the person's answers and listing your own work need a seat: offer to set one (the last section). - Call `rig_team` with the rig's name: it shows the team's seats, what each is for, and its lead. Work goes to the lead unless the person names a seat. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_veh7dlykrnduhm7n/7cfa6ebd30ab229e76de47d2b3ab570bc98f286d3de9cc4ac22fd2d0239daf80.json
Then /plugin install working-with-an-openrig-team@markdownregistry-veh7dlykrnduhm7n in Claude Code. It installs git:20261115.861710b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mvschwarz/openrig/working-with-an-openrig-team@sha256:7cfa6ebd30ab229eThe line at the top of this page pins the label git:20261115.861710b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_veh7dlykrnduhm7n)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in mvschwarz/openrig/working-with-an-openrig-team since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of working-with-an-openrig-team from somewhere else? Ask it: where did my working-with-an-openrig-team come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 6 versions of this file, between Nov 7, 2026 and Nov 15, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261115.861710b latest | 2026-11-15 | 861710b | 8,337 B | A | view · diff |
| git:20261112.59aa8df | 2026-11-12 | 59aa8df | 6,709 B | A | view · diff |
| git:20261108.8a46d8f | 2026-11-08 | 8a46d8f | 6,100 B | A | view · diff |
| git:20261108.0f88021 | 2026-11-08 | 0f88021 | 6,059 B | A | view · diff |
| git:20261107.7f3b85e | 2026-11-07 | 7f3b85e | 5,801 B | A | view · diff |
| git:20261107.772fa5c | 2026-11-07 | 772fa5c | 5,601 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/working-with-an-openrig-team/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8337 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mvschwarz/openrig · 8,889 stars · license Apache-2.0 · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_veh7dlykrnduhm7n GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/working-with-an-openrig-team GET https://markdownregistry.com/api/v1/blob/7cfa6ebd30ab229e76de47d2b3ab570bc98f286d3de9cc4ac22fd2d0239daf80
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from mvschwarz/openrig
Every file in mvschwarz/openrig