New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Developing Openrig

by mvschwarz in mvschwarz/openrig

A skill your agent uses 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…

Apache-2.0Auto-check passedDevelopment

Install Developing Openrig

skills CLI
$ npx skills add mvschwarz/openrig --skill developing-openrig -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mvschwarz/openrig developing-openrig --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/developing-openrig .claude/skills/developing-openrig && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
developing-openrig
GitHub stars
5.5k
Token cost
~1.5k tokens
SKILL.md length
789 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses 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…

  • Works in 3 steps: Read the artery row: what depends on it,… → Describe the downstream effect in your… → Add or extend a stub-agent scenario, or…
  • Changing OpenRigs own source in a clone of the openrig repository: finding which package
  • SKILL.md covers First: which OpenRig are you in?, Find your way, Before you change an artery and Test it, plus 2 more sections
  • Calls npm and git

What it does

Developing Openrig is an agent skill from mvschwarz/openrig. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. The licence is Apache-2.0.

When your agent uses it

  • Changing OpenRigs own source in a clone of the openrig repository: finding which package
  • File owns a behaviour
  • Choosing which tests to run
  • Testing a change without disturbing the OpenRig daemon your own session runs on

Example prompts

  • “/developing-openrig”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Read the artery row: what depends on it, and the past regressions listed there.
  2. Describe the downstream effect in your pull request, not just the diff.
  3. Add or extend a stub-agent scenario, or say precisely why the stub can't exercise it and what you ran instead.

What it can do on your machine

Read from SKILL.md and the folder at commit a7fed63. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Developing Openrig loads about 1.5k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 789 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~100
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mvschwarz/openrig at commit a7fed63, republished under its Apache-2.0 licence (© mvschwarz). 789 words, ~1,492 tokens.

Download SKILL.mdSave it as .claude/skills/developing-openrig/SKILL.md (or your agent's skills folder).
name
developing-openrig
description
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.

Developing OpenRig

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.

First: which OpenRig are you in?

If you are an agent running inside OpenRig, two different OpenRigs are in play:

  • The installed one runs your session. rig --version and rig daemon status describe it.
  • The checkout is what you're changing. 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.

Find your way

You want to knowReadHow much to trust it
What OpenRig can already do, before you decide something is missingrig context get onboarding-width/public-what-you-can-do.md; in this checkout, packages/daemon/context-packs-src/onboarding-width/public-what-you-can-do.md (the installed copy can differ)The capability map; check it before proposing a new command or calling a gap a defect
Whether a rig command already existsrig --help: the full command list, before you decide a command is missingThe running binary; read the whole list, not only the command you expected
Whether a problem is already knownThe "Known problems to compare against" section of docs/reference/help.mdLists known issues by symptom; check an issue's current status before relying on it
Whether a feature is already plannedROADMAP.mdCheck it before proposing a feature
How the packages fit, the request path, where to add a command, route, migration, adapter, skill, context pack or scenarioARCHITECTURE.mdChecked against the commit it names; counts come with the command to refresh them
Whether your change touches a high-risk area, what depends on it, what broke there beforedocs/as-built/arteries.mdIncomplete by design: absence from it doesn't make a change safe
What to run before you push, and what each layer can and can't provedocs/as-built/test-layers.mdChecked against the commit it names
The exact behaviour of a rig commandrig <command> --help on the running binary, then packages/cli/src/commands/The binary and the code win over any document
A subsystem in depthdocs/as-built/Each module names the commit it was last checked against in last-verified-against-source; compare that marker with git log before relying on it
Rig spec, agent spec and other user-facing referencedocs/reference/Ships to every user; if you find drift, fix it there
Which shipped skill covers a taskskills/_canonical/core/openrig-skills/SKILL.mdThe index of the skills that ship with OpenRig
How to open a good pull request, and what review looks likeCONTRIBUTING.mdCurrent

If none of these answers your question, search the code before inventing an answer. A missing map is worth an issue.

Show full SKILL.md (325 more words)Show less

Before you change an artery

If your diff touches anything in arteries.md (message delivery, launch and resume, the queue, rig identity, skill projection, process observation, migrations, restore):

  1. Read the artery row: what depends on it, and the past regressions listed there.
  2. Describe the downstream effect in your pull request, not just the diff.
  3. Add or extend a stub-agent scenario, or say precisely why the stub can't exercise it and what you ran instead.

Test it

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.

  • The scenario runner starts its own daemon and tmux server and drops your session's TMUX and daemon variables, so it won't touch the daemon your session runs on.
  • A stub proves OpenRig's own plumbing, not how Claude Code or Codex behave. Say which you exercised.

How we judge changes

OpenRig is a coordination layer for a trusted environment: it should help agents and people keep work flowing.

  • A change that removes friction, or makes state more truthful, is usually welcome.
  • OpenRig runs on agents working in context with tools. Before adding code for a behaviour, ask whether an agent with the right instructions and today's commands could do it. A skill or a page of guidance is often the better change.
    • Where to look: the capability map above, and the agent-operated-workflows skill, which ships in the openrig-core plugin (packages/daemon/assets/plugins/openrig-core/skills/agent-operated-workflows/SKILL.md).
  • A change that adds a refusal, a prompt or a required step needs the concrete case in CONTRIBUTING.md: who is harmed, how, and what it costs everyone else.
  • One concern per pull request. Keep the diff reviewable in one sitting.

When the map is wrong

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.

© mvschwarz, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/developing-openrig of mvschwarz/openrig.

Open the folder on GitHubat commit a7fed63

Compare with similar skills

Developing Openrig next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Developing Openrig compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Developing Openrig this skillmvschwarz/openrig5.5k—~1.5kAutomated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from mvschwarz/openrig

All 49 skills in this repo

  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    5.5k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • OpenRig Software Factory

    mvschwarz/openrig

    Helps set up a continuing agent software team for a real repository with OpenRig, choosing between manual work, queue handoffs and an explicit Workflow.

    5.5k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Seat Continuity and Handover

    mvschwarz/openrig

    Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.

    5.5k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Addressable Markdown Loader

    mvschwarz/openrig

    Loads one section of a Markdown file by its path#h2-slug address with a bundled resolver script, for use outside OpenRig's context library.

    5.5k GitHub stars~341 tokensUpdated today
    Auto-check passed

  • Vault User

    mvschwarz/openrig

    A skill your agent uses when checking the health of this rig's HashiCorp Vault or writing, reading, listing, deleting or explaining its secrets.

    5.5k GitHub starsUsed in 1 repo~451 tokens
    Auto-check passed

  • Agent Refocusing

    mvschwarz/openrig

    Re-grounds a long-running agent in the current product outcome by running a path-based trace to the root of its topology and work trees.

    5.5k GitHub stars~399 tokensUpdated today
    Auto-check passed

Categories

Questions about Developing Openrig

What does Developing Openrig do?

A skill your agent uses 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…. Developing Openrig is an agent skill from mvschwarz/openrig. 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.

When should I use Developing Openrig?

Developing Openrig fits situations like: changing OpenRigs own source in a clone of the openrig repository: finding which package; file owns a behaviour; choosing which tests to run; testing a change without disturbing the OpenRig daemon your own session runs on.

How do I install Developing Openrig in Claude Code?

Run `npx skills add mvschwarz/openrig --skill developing-openrig -a claude-code`. Or copy the skill folder (.agents/skills/developing-openrig in mvschwarz/openrig) into .claude/skills/developing-openrig in your project. Claude Code loads it when a task matches its description.

How do I install Developing Openrig in Codex?

Run `npx skills add mvschwarz/openrig --skill developing-openrig -a codex`. Or copy the skill folder (.agents/skills/developing-openrig in mvschwarz/openrig) into .agents/skills/developing-openrig in your project. Codex loads it when a task matches its description.

Can I use Developing Openrig in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvschwarz/openrig --skill developing-openrig -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developing-openrig, .gemini/skills/developing-openrig, .github/skills/developing-openrig and .opencode/skills/developing-openrig in your project.

What does Developing Openrig need to run?

Going by SKILL.md and its folder, Developing Openrig needs the command-line tools its instructions call (npm and git).

Does Developing Openrig access the network?

SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Developing Openrig safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Developing Openrig use?

Developing Openrig is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Developing Openrig use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Developing Openrig?

Skills that share tags, products or a category with Developing Openrig: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Developing Openrig?

mvschwarz (a GitHub user) maintains it in mvschwarz/openrig, which has 5,542 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 7, 2026.

Source: mvschwarz/openrig on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.