[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMHAVYBA89Y68VK9RMVAPK":3,"skill-same:01M7DMHAVYBA89Y68VK9RMVAPK":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7DMHAVYBA89Y68VK9RMVAPK","developing-openrig",null,"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.","mvschwarz\u002Fopenrig-world","mvschwarz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171890339?v=4","01M7DM95A4N5936P8G2FTSPMY7","Mike Schwarz","01M7DM95AX80NY8HZA7XXDYAZR",16,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop-review-pair\u002Fagents\u002Fworkshop\u002Fskills\u002Fdeveloping-openrig\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: developing-openrig\ndescription: \"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.\"\n---\n\n# Developing OpenRig\n\nThis skill is a map to the other maps. Each one is incomplete and may be stale: where a map and the code disagree, the\ncode is right, and fixing the map is a welcome contribution.\n\n## First: which OpenRig are you in?\n\nIf you are an agent running inside OpenRig, two different OpenRigs are in play:\n\n- **The installed one runs your session.** `rig --version` and `rig daemon status` describe it.\n- **The checkout is what you're changing.** `git rev-parse HEAD` describes it.\n\nRestarting the installed daemon does not run your checkout, and stopping it stops the agents running on it, including\nyou. Test your change with the repo's own harnesses, which start a private daemon and tmux server (see \"Test it\" below),\nnot by restarting the daemon you live in.\n\n## Find your way\n\n| You want to know | Read | How much to trust it |\n|---|---|---|\n| What OpenRig can already do, before you decide something is missing | `rig context get onboarding-width\u002Fpublic-what-you-can-do.md`; in this checkout, `packages\u002Fdaemon\u002Fcontext-packs-src\u002Fonboarding-width\u002Fpublic-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 |\n| Whether a `rig` command already exists | `rig --help`: the full command list, before you decide a command is missing | The running binary; read the whole list, not only the command you expected |\n| Whether a problem is already known | The \"Known problems to compare against\" section of [`docs\u002Freference\u002Fhelp.md`](..\u002F..\u002F..\u002Fdocs\u002Freference\u002Fhelp.md) | Lists known issues by symptom; check an issue's current status before relying on it |\n| Whether a feature is already planned | [`ROADMAP.md`](..\u002F..\u002F..\u002FROADMAP.md) | Check it before proposing a feature |\n| How the packages fit, the request path, where to add a command, route, migration, adapter, skill, context pack or scenario | [`ARCHITECTURE.md`](..\u002F..\u002F..\u002FARCHITECTURE.md) | Checked against the commit it names; counts come with the command to refresh them |\n| Whether your change touches a high-risk area, what depends on it, what broke there before | [`docs\u002Fas-built\u002Farteries.md`](..\u002F..\u002F..\u002Fdocs\u002Fas-built\u002Farteries.md) | Incomplete by design: absence from it doesn't make a change safe |\n| What to run before you push, and what each layer can and can't prove | [`docs\u002Fas-built\u002Ftest-layers.md`](..\u002F..\u002F..\u002Fdocs\u002Fas-built\u002Ftest-layers.md) | Checked against the commit it names |\n| The exact behaviour of a `rig` command | `rig \u003Ccommand> --help` on the running binary, then `packages\u002Fcli\u002Fsrc\u002Fcommands\u002F` | The binary and the code win over any document |\n| A subsystem in depth | [`docs\u002Fas-built\u002F`](..\u002F..\u002F..\u002Fdocs\u002Fas-built\u002FREADME.md) | 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 |\n| Rig spec, agent spec and other user-facing reference | [`docs\u002Freference\u002F`](..\u002F..\u002F..\u002Fdocs\u002Freference\u002F) | Ships to every user; if you find drift, fix it there |\n| Which shipped skill covers a task | [`skills\u002F_canonical\u002Fcore\u002Fopenrig-skills\u002FSKILL.md`](..\u002F..\u002F..\u002Fskills\u002F_canonical\u002Fcore\u002Fopenrig-skills\u002FSKILL.md) | The index of the skills that ship with OpenRig |\n| How to open a good pull request, and what review looks like | [`CONTRIBUTING.md`](..\u002F..\u002F..\u002FCONTRIBUTING.md) | Current |\n\nIf none of these answers your question, search the code before inventing an answer. A missing map is worth an issue.\n\n## Before you change an artery\n\nIf your diff touches anything in `arteries.md` (message delivery, launch and resume, the queue, rig identity, skill\nprojection, process observation, migrations, restore):\n\n1. Read the artery row: what depends on it, and the past regressions listed there.\n2. Describe the downstream effect in your pull request, not just the diff.\n3. Add or extend a stub-agent scenario, or say precisely why the stub can't exercise it and what you ran instead.\n\n## Test it\n\nThe short version is `npm run build`, `npm run lint`, `npm test`. `test-layers.md` has the full ladder, including the\nstub-agent scenarios, which run the real CLI, daemon, tmux and SQLite with scripted agents and no model cost.\n\n- The scenario runner starts its own daemon and tmux server and drops your session's `TMUX` and daemon variables, so\n  it won't touch the daemon your session runs on.\n- A stub proves OpenRig's own plumbing, not how Claude Code or Codex behave. Say which you exercised.\n\n## How we judge changes\n\nOpenRig is a coordination layer for a trusted environment: it should help agents and people keep work flowing.\n\n- A change that removes friction, or makes state more truthful, is usually welcome.\n- OpenRig runs on agents working in context with tools. Before adding code for a behaviour, ask whether an agent with\n  the right instructions and today's commands could do it. A skill or a page of guidance is often the better change.\n  - Where to look: the capability map above, and the `agent-operated-workflows` skill, which ships in the\n    `openrig-core` plugin (`packages\u002Fdaemon\u002Fassets\u002Fplugins\u002Fopenrig-core\u002Fskills\u002Fagent-operated-workflows\u002FSKILL.md`).\n- A change that adds a refusal, a prompt or a required step needs the concrete case in CONTRIBUTING.md: who is\n  harmed, how, and what it costs everyone else.\n- One concern per pull request. Keep the diff reviewable in one sitting.\n\n## When the map is wrong\n\nFix it in the same pull request, or open an issue. Update a document's `last-verified-against-source` marker only when\nyou have actually checked it against that commit.\n","# Developing OpenRig\n\nThis skill is a map to the other maps. Each one is incomplete and may be stale: where a map and the code disagree, the\ncode is right, and fixing the map is a welcome contribution.\n\n## First: which OpenRig are you in?\n\nIf you are an agent running inside OpenRig, two different OpenRigs are in play:\n\n- **The installed one runs your session.** `rig --version` and `rig daemon status` describe it.\n- **The checkout is what you're changing.** `git rev-parse HEAD` describes it.\n\nRestarting the installed daemon does not run your checkout, and stopping it stops the agents running on it, including\nyou. Test your change with the repo's own harnesses, which start a private daemon and tmux server (see \"Test it\" below),\nnot by restarting the daemon you live in.\n\n## Find your way\n\n| You want to know | Read | How much to trust it |\n|---|---|---|\n| What OpenRig can already do, before you decide something is missing | `rig context get onboarding-width\u002Fpublic-what-you-can-do.md`; in this checkout, `packages\u002Fdaemon\u002Fcontext-packs-src\u002Fonboarding-width\u002Fpublic-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 |\n| Whether a `rig` command already exists | `rig --help`: the full command list, before you decide a command is missing | The running binary; read the whole list, not only the command you expected |\n| Whether a problem is already known | The \"Known problems to compare against\" section of [`docs\u002Freference\u002Fhelp.md`](..\u002F..\u002F..\u002Fdocs\u002Freference\u002Fhelp.md) | Lists known issues by symptom; check an issue's current status before relying on it |\n| Whether a feature is already planned | [`ROADMAP.md`](..\u002F..\u002F..\u002FROADMAP.md) | Check it before proposing a feature |\n| How the packages fit, the request path, where to add a command, route, migration, adapter, skill, context pack or scenario | [`ARCHITECTURE.md`](..\u002F..\u002F..\u002FARCHITECTURE.md) | Checked against the commit it names; counts come with the command to refresh them |\n| Whether your change touches a high-risk area, what depends on it, what broke there before | [`docs\u002Fas-built\u002Farteries.md`](..\u002F..\u002F..\u002Fdocs\u002Fas-built\u002Farteries.md) | Incomplete by design: absence from it doesn't make a change safe |\n| What to run before you push, and what each layer can and can't prove | [`docs\u002Fas-built\u002Ftest-layers.md`](..\u002F..\u002F..\u002Fdocs\u002Fas-built\u002Ftest-layers.md) | Checked against the commit it names |\n| The exact behaviour of a `rig` command | `rig \u003Ccommand> --help` on the running binary, then `packages\u002Fcli\u002Fsrc\u002Fcommands\u002F` | The binary and the code win over any document |\n| A subsystem in depth | [`docs\u002Fas-built\u002F`](..\u002F..\u002F..\u002Fdocs\u002Fas-built\u002FREADME.md) | 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 |\n| Rig spec, agent spec and other user-facing reference | [`docs\u002Freference\u002F`](..\u002F..\u002F..\u002Fdocs\u002Freference\u002F) | Ships to every user; if you find drift, fix it there |\n| Which shipped skill covers a task | [`skills\u002F_canonical\u002Fcore\u002Fopenrig-skills\u002FSKILL.md`](..\u002F..\u002F..\u002Fskills\u002F_canonical\u002Fcore\u002Fopenrig-skills\u002FSKILL.md) | The index of the skills that ship with OpenRig |\n| How to open a good pull request, and what review looks like | [`CONTRIBUTING.md`](..\u002F..\u002F..\u002FCONTRIBUTING.md) | Current |\n\nIf none of these answers your question, search the code before inventing an answer. A missing map is worth an issue.\n\n## Before you change an artery\n\nIf your diff touches anything in `arteries.md` (message delivery, launch and resume, the queue, rig identity, skill\nprojection, process observation, migrations, restore):\n\n1. Read the artery row: what depends on it, and the past regressions listed there.\n2. Describe the downstream effect in your pull request, not just the diff.\n3. Add or extend a stub-agent scenario, or say precisely why the stub can't exercise it and what you ran instead.\n\n## Test it\n\nThe short version is `npm run build`, `npm run lint`, `npm test`. `test-layers.md` has the full ladder, including the\nstub-agent scenarios, which run the real CLI, daemon, tmux and SQLite with scripted agents and no model cost.\n\n- The scenario runner starts its own daemon and tmux server and drops your session's `TMUX` and daemon variables, so\n  it won't touch the daemon your session runs on.\n- A stub proves OpenRig's own plumbing, not how Claude Code or Codex behave. Say which you exercised.\n\n## How we judge changes\n\nOpenRig is a coordination layer for a trusted environment: it should help agents and people keep work flowing.\n\n- A change that removes friction, or makes state more truthful, is usually welcome.\n- OpenRig runs on agents working in context with tools. Before adding code for a behaviour, ask whether an agent with\n  the right instructions and today's commands could do it. A skill or a page of guidance is often the better change.\n  - Where to look: the capability map above, and the `agent-operated-workflows` skill, which ships in the\n    `openrig-core` plugin (`packages\u002Fdaemon\u002Fassets\u002Fplugins\u002Fopenrig-core\u002Fskills\u002Fagent-operated-workflows\u002FSKILL.md`).\n- A change that adds a refusal, a prompt or a required step needs the concrete case in CONTRIBUTING.md: who is\n  harmed, how, and what it costs everyone else.\n- One concern per pull request. Keep the diff reviewable in one sitting.\n\n## When the map is wrong\n\nFix it in the same pull request, or open an issue. Update a document's `last-verified-against-source` marker only when\nyou have actually checked it against that commit.\n",{"name":5,"description":7},"main","60438a272b68d091eddb01aad6e399af4996d536","rigs\u002Fworkshop-review-pair\u002Fagents\u002Fworkshop\u002Fskills\u002Fdeveloping-openrig",4,"https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world","https:\u002F\u002Fgithub.com\u002Fmvschwarz","https:\u002F\u002Fopenrig.dev","Building OpenRig. Running rogue AI civilizations. Debugging their coordination problems.","2026-11-12 13:31:38",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add mvschwarz\u002Fopenrig-world --skill developing-openrig",{"tool":39,"command":40},"bunx","bunx skills add mvschwarz\u002Fopenrig-world --skill developing-openrig",{"tool":42,"command":43},"pnpm","pnpm dlx skills add mvschwarz\u002Fopenrig-world --skill developing-openrig","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop-review-pair\u002Fagents\u002Fworkshop\u002Fskills\u002Fdeveloping-openrig\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7DMSEDCRREMBJF57RQB59HC","notes","Use when taking notes.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Ftools\u002Ftest\u002Ffixtures\u002Finstall-verify\u002Fbundle\u002Fagents\u002Fteam\u002Fskills\u002Fnotes\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7DMSBZP9WE8MC09JDXFCR2F","software-for-agents","Use when older OpenRig instructions name software-for-agents or describe agent-in-the-middle or studio software under the former skill name.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fsoftware-for-agents\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DMS55VHEAGPXMHZJ7FX94R","session-compaction-and-restore","Use when reasoning about what survives compaction\u002Fcontext-loss\u002Frestart\u002Fseat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental-model rebuild. Covers the 4 failure modes that prevent honest restore (compacted seat drops hot potato; restore packet preserves details but loses product intent; runtime resume mistaken for handover or fork; rebuilt seat starts with stale instructions).","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fsession-compaction-and-restore\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DMRYQK0JTV7MMVHFWZ0BW0","seat-continuity-and-handover","Use when replacing a seat's occupant (rebuild\u002Fhandover\u002Fswap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant disposition (retire\u002Fadvise\u002Fshadow), or recording provenance for an occupant change. Two independent outcomes (continuityOutcome + seatBindingOutcome) and the 5 failure modes that prevent silent dishonesty.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fseat-continuity-and-handover\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DMRP6RRGCJZSH9CE3PC1MY","retiring-and-inheriting-a-seat","Use when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per tenure), physical-seat continuity, the do-not-over-inherit framing, the optional warm-handoff window, and wake-v0 (consulting a retired predecessor). NOT for unplanned compaction\u002Fcrash recovery (session-compaction-and-restore \u002F claude-compaction-restore) and NOT the seat-binding primitive mechanics (seat-continuity-and-handover).","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fretiring-and-inheriting-a-seat\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DMRJGN6Z8TZDR7JNHXH6KX","refocusing","Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Frefocusing\u002FSKILL.md",[],[]]