openrig-operating-model SKILL.md skillA
openrig-operating-model 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/openrig-operating-model@git:20261004.9e24dffPins git:20261004.9e24dff 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-core/skills/openrig-operating-model/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261004.9e24dff, committed Oct 4, 2026
- First version recorded
- Aug 27, 2026
- Size
- 24,942 bytes
- Repository stars
- 8,889
- License
- Apache-2.0
Use when you do not know WHERE something belongs: you learned a lesson and are unsure which file takes it; you are about to create a new doc, folder, or convention; you are asking "should this be a skill, a note, or a chain file?"; you inherited a seat and want to know what SHOULD exist; or you are about to duplicate knowledge that already has a home. Also the trace-to-root: how a seat orients by reading one filename at each level from where it stands up to the fleet.
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
# The OpenRig Operating Model **Canonical term: the Operating Model.** How an OpenRig topology organizes every kind of context so that any agent — cold, fresh, or five generations in — can find what it needs and knows where to write what it learns. Authored context stays in addressed Markdown and manifests. Supported writers record semantic judgments; their read models remain rebuildable from those artifacts. This skill owns the structure: trees, chains, tracing, and placement of authored knowledge. Resolve installed context through its current library addresses and the project's selected loadout; a private corpus is not a required public dependency. Companion implementation assets in this skill's folder: - `templates/` and `scripts/` — starters and working tools, described in §8. ## 1. The model in one breath Everything lives on one of **two trees**, and every kind of context is a **chain**: the same filename at every level of a tree. To know anything, you **trace from where you are toward the root**, reading that one filename at each level — nearer levels refine or override farther ones. The **trace** (§5) is …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lxdunvo7r27hvhtq/8364530a6199f6e2df42b773c35434cb4ecade0ede48e439cd9fc03df4469896.json
Then /plugin install openrig-operating-model@markdownregistry-lxdunvo7r27hvhtq in Claude Code. It installs git:20261004.9e24dff, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mvschwarz/openrig/openrig-operating-model@sha256:8364530a6199f6e2The line at the top of this page pins the label git:20261004.9e24dff, 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_lxdunvo7r27hvhtq)
7 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/openrig-operating-model 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 openrig-operating-model from somewhere else? Ask it: where did my openrig-operating-model 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 Aug 27, 2026 and Oct 4, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261004.9e24dff latest | 2026-10-04 | 9e24dff | 24,942 B | A | view · diff |
| git:20260908.e4e15c6 | 2026-09-08 | e4e15c6 | 23,720 B | A | view · diff |
| git:20260907.386e515 | 2026-09-07 | 386e515 | 22,515 B | A | view · diff |
| git:20260830.44ea56a | 2026-08-30 | 44ea56a | 23,591 B | A | view · diff |
| git:20260827.3343472 | 2026-08-27 | 3343472 | 24,090 B | A | view · diff |
| git:20260827.cf379bd | 2026-08-27 | cf379bd | 23,524 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/openrig-operating-model/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 (24942 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_lxdunvo7r27hvhtq GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/openrig-operating-model GET https://markdownregistry.com/api/v1/blob/8364530a6199f6e2df42b773c35434cb4ecade0ede48e439cd9fc03df4469896
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.