openrig-skills 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.
openrig-skills 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-skills@git:20261107.772fa5cPins git:20261107.772fa5c 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-skills/SKILL.md- Versions recorded
- 14
- Latest version
- git:20261107.772fa5c, committed Nov 7, 2026
- First version recorded
- Sep 1, 2026
- Size
- 11,009 bytes
- Repository stars
- 8,889
- License
- Apache-2.0
Use when an agent running inside OpenRig needs the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade, systematic debugging, queue triage, or implementation planning; also when the agent doesn't know what applies or nothing is projected on cold boot. Installing, starting or updating OpenRig, getting back to a team or bringing a stopped one back from a person's own…
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
# OpenRig skills — the index (start here) You're running inside OpenRig. OpenRig ships a set of **skills** — small documents that tell you *when* to do something and *how*. This file is the map: what ships, when to reach for each, and how to load it. If you don't know which skill applies, or nothing is projected into your context, **start here.** ## How OpenRig context works (30 seconds) Skills are **progressive disclosure**: a skill's *name + description* sit in your context ambiently (the "hot tier"); its *body* loads only when you open it. So you don't pre-read everything — you pattern-match a skill's "when" to your moment, then open just that one. This file recommends skills from the shipped set. (For bounded procedures, open `agent-operated-workflows`; for ongoing agent-backed applications, open `agent-operated-software`.) Every row below names **how to reach the skill** — already-hot, or an exact load path. No row is a dead end. ## Loading an entry on demand — `rig context get` Don't guess a file path or a name. Go **ask → ref → load** in three steps: 1. **Discover** — run `rig context list` for every shipped entry's **ref** and name. The *when* for …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_k56ztyrw7zyqiiws/6d7bf933ac40531f11757a31a93d26dcbda617f1b85f48a21865b3a5c5e2ddaa.json
Then /plugin install openrig-skills@markdownregistry-k56ztyrw7zyqiiws in Claude Code. It installs git:20261107.772fa5c, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mvschwarz/openrig/openrig-skills@sha256:6d7bf933ac40531fThe line at the top of this page pins the label git:20261107.772fa5c, 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_k56ztyrw7zyqiiws)
4 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-skills 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-skills from somewhere else? Ask it: where did my openrig-skills 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 14 versions of this file, between Sep 1, 2026 and Nov 7, 2026, about one every 5 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261107.772fa5c latest | 2026-11-07 | 772fa5c | 11,009 B | A | view · diff |
| git:20261021.0b63f94 | 2026-10-21 | 0b63f94 | 10,625 B | A | view · diff |
| git:20261018.ce7f89c | 2026-10-18 | ce7f89c | 10,611 B | A | view · diff |
| git:20261012.ada3678 | 2026-10-12 | ada3678 | 10,531 B | A | view · diff |
| git:20261007.2ef93ad | 2026-10-07 | 2ef93ad | 10,380 B | A | view · diff |
| git:20261006.d1e9d5e | 2026-10-06 | d1e9d5e | 10,352 B | A | view · diff |
| git:20261006.fcef78a | 2026-10-06 | fcef78a | 10,435 B | A | view · diff |
| git:20261001.792ef42 | 2026-10-01 | 792ef42 | 10,432 B | A | view · diff |
| git:20260929.61f13f6 | 2026-09-29 | 61f13f6 | 10,302 B | A | view · diff |
| git:20260925.4940c10 | 2026-09-25 | 4940c10 | 9,926 B | A | view · diff |
| git:20260924.b131334 | 2026-09-24 | b131334 | 9,842 B | A | view · diff |
| git:20260924.767cc70 | 2026-09-24 | 767cc70 | 9,821 B | A | view · diff |
| git:20260904.e952d4e | 2026-09-04 | e952d4e | 9,595 B | A | view · diff |
| git:20260901.0b86028 | 2026-09-01 | 0b86028 | 9,230 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-skills/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 (11009 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_k56ztyrw7zyqiiws GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/openrig-skills GET https://markdownregistry.com/api/v1/blob/6d7bf933ac40531f11757a31a93d26dcbda617f1b85f48a21865b3a5c5e2ddaa
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