mvschwarz/openrig / skills/_canonical/core/working-with-an-openrig-team
working-with-an-openrig-team
VerifiedUse 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.
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_whoaminames, with no return address, so tell the person theqitemIdand follow it withrig_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_teamwith 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. - If
leadis null (itsleadNotesays why), and the team has exactly one seat, send work there. Otherwise, ask the person which seat should take it.
Hand the team work
-
Use
rig_queue_createwithdestination(the lead, or the seat the person chose) andbody. Write the body for a capable colleague: the goal, why it matters, what done looks like, and where to look. Add a one-linesummary. -
With a seat, end the body with the reply route, because your seat has no terminal and
rig sendcan't reach it:To ask me anything, create a queue item to
<your seat>(rig queue create --destination <your seat> ...), then block this item on that new item's id (rig queue block <this id> --on <question id>), so my answer wakes you. I check it whenever the person talks to me. Don't ask in your own terminal: the person isn't there. A seat's permission prompt in this work is their question too: send me its own text and choices, the seat, what it was doing and any escalation's id, unless a question about that prompt is already open at my seat. Whoever sent the question passes on the answer, and no one else does. Capture that seat again first (a changed prompt needs a new answer), thenrig send <seat> "<key>" --dangerously-interact --reason 'task <question id>: <their answer>'with the key the prompt shows for their choice (for Escape,$'\e'in place of"<key>", never the word). Keep the reason in single quotes so the shell runs nothing in their words, and write each'in them as'\''. A no stays a no. If they gave no answer, or their words don't clearly pick one choice (a condition the action doesn't plainly meet, say), ask me again before sending anything, and never pick a "don't ask again" choice they didn't pick. Check the effect, and never send again while it's unknown. If you hand this item on or give this work to another seat, copy this paragraph into the new item. When you finish, put the outcome in this item's resolution, with what the latest review found, and any file in its evidence ref. -
Tell the person the
qitemIdit returns. It's how both of you find this work again. -
If the call times out, check
rig_queue_showwith that sameqitemIdbefore trying again. If you retry, pass the same id asqitemId. Never retry with a new one: that creates the work twice.
Follow it
rig_queue_showwith theqitemIdgives its state, its current owner and its transitions.- When a seat hands the work on, the item names the next one. Follow the chain to the newest item before you report.
- Report what the record says. An accepted or claimed item isn't finished work, and a quiet one isn't stuck: say what you saw and when it last changed.
- Before you say the work is done, find the newest review of it on the chain and tell the person its outcome. Work a review sent back with something to fix isn't done, even if a commit exists: say what the review asked for.
- Nothing wakes this chat when the team asks or finishes. While its work is open, check each time the person talks to you, and when they come back.
The team's questions
- Questions about your work come to your seat:
rig_queue_listwithownedlists them. - Show the person the question and the team's draft, in their own words where the item gives them. Then ask for an answer.
- Record only what the person actually tells you. Claim the item (
rig_queue_claim), then close it withrig_queue_update:statedone,closureReasonno-follow-on, and exactly what the person typed inresolution, nothing else: no label such as "The person's answer:", no quotation marks, and no notes, paths or summaries of your own. If the person isn't there to answer, leave the item open and tell them it's waiting. Never choose an answer for them. - A question can be a seat's permission prompt that the operator or a team seat sent you: show it with the seat, the exact action and the choices it offers, and record the person's words the same way. The agent that sent it passes their answer to the seat.
- Some questions go to a registered person directly, outside your seat. Those wait for them where they already answer the team, such as the OpenRig TUI or Slack. You can mention that they're waiting; answering them isn't yours.
Read the result
- When the item is
done, itsresolutionis the answer, and its transitions hold the notes the team recorded. - If it names an
evidenceRef, read it withrig_artifact_read, passing the item'sqitemId, not the path. The tool reads the item'sevidenceRefwithin the shared roots this connection may read. For another file in a shared root, pass the root's name andpath. If the connection can't read it, give the person the path. - To ask for changes, create a new item with
revisesset to the earlierqitemId, so the revision stays with the original work.
Come back later
rig_queue_listwithminelists what this seat sent or owns. Addallto include finished work, orsinceto see what changed after a time.- A new chat with the same seat reaches the same work. Items outlive conversations.
Set it up (once, with the person)
- OpenRig runs on this machine with a team:
rig pslists the person's rigs. - Pick an address for this app on one of those rigs, for example
cursor@my-team. It's an address the queue takes items for; nothing is launched for it. To tell the team what it's for, the person can add it to a roster as a hosted member (docs/reference/hosted-members.mdin the OpenRig package). - Connect the app to that address, then start a new session so the MCP server starts with it:
- Claude Code: set it as the plugin's OpenRig seat in the plugin's settings.
- Codex: run
codex mcp add openrig --env OPENRIG_SESSION_NAME=<address> -- rig mcp serve --front-door. Codex does not forward every shell environment variable to MCP servers by default, so if the team's OpenRig home isn't the default, add--env OPENRIG_HOME=<that home>too. - Another app: add an MCP server that runs
rig mcp serve --front-doorwithOPENRIG_SESSION_NAMEset to the address, and turn the plugin'sopenrigserver off, so the app runs one. In VS Code, give yours another name, such asopenrig-seat; in Cursor, disable openrig · Plugin. Starting the app from a shell with the variable set lasts only for that launch.
What this doesn't do
- It doesn't add a panel to the app, and nothing wakes this chat when the team finishes.
- Anyone using this app on this machine acts as the seat the plugin names.
- It reaches a team on this machine. A team hosted elsewhere needs that host's own connection.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |