specification-system SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
specification-system 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/specification-system@git:20260802.4c6d888Pins git:20260802.4c6d888 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mvschwarz/openrig
- Path
skills/_canonical/core/specification-system/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260802.4c6d888, committed Aug 2, 2026
- Size
- 4,931 bytes
- Repository stars
- 8,889
- License
- Apache-2.0
Use when authoring rig specs, agent specs, workflow specs, startup/context fragments, operating-mode declarations, or designing the user spec library. Covers the 4 failure modes (spec instantiates topology but not workflow/mode; spec depends on local paths and fails on another host; agents modify specs as one-off files instead of preserving reusable intent; validation proves YAML shape but not whether topology can run) and the validation-vs-runtime-realization distinction.
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
# Specification System The declarative primitive family for OpenRig intent: **rig specs, agent specs, workflow specs, startup/context fragments, operating-mode declarations, and the user spec library that stores and reuses them.** Specs are how humans and agents describe **repeatable topology and behavior** without re-explaining it in chat. They are also shareable artifacts: a user should be able to publish a spec or spec family so another user can instantiate the same rig shape, role structure, or workflow pattern. **Without a dependable spec primitive, OpenRig depends on manual startup prompts and tribal memory.** That blocks repeatability, product demos, rig bundles, and autonomous rig construction. ## Use this when - Authoring a RigSpec / AgentSpec / workflow spec - Designing a startup/context fragment - Reasoning about spec-library lifecycle (validation, sharing, upgrade semantics) - Auditing a spec for portability (does it run on another host?) - Distinguishing spec vs bundle vs extension cleanly ## Don't use this when - The work is one-off and won't be reused. Manual rig assembly is fine for one-shot work. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_zu3ccz37r4d6uuh6/5226d6e8b1362df89ba3d5afd82e4b4add355870132ca4b140d7f9f4324ffdc1.json
Then /plugin install specification-system@markdownregistry-zu3ccz37r4d6uuh6 in Claude Code. It installs git:20260802.4c6d888, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mvschwarz/openrig/specification-system@sha256:5226d6e8b1362df8The line at the top of this page pins the label git:20260802.4c6d888, 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_zu3ccz37r4d6uuh6)
3 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/specification-system 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 specification-system from somewhere else? Ask it: where did my specification-system 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 1 version of this file, committed on Aug 2, 2026.
Watch this file (sign in, one email per new version)
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/specification-system/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 (4931 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_zu3ccz37r4d6uuh6 GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/specification-system GET https://markdownregistry.com/api/v1/blob/5226d6e8b1362df89ba3d5afd82e4b4add355870132ca4b140d7f9f4324ffdc1
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