setup SKILL.md skillB
setup from q00/ouroboros is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add q00/ouroboros/setup@git:20261117.c0a64b7Pins git:20261117.c0a64b7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- q00/ouroboros
- Path
skills/setup/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261117.c0a64b7, committed Nov 17, 2026
- First version recorded
- Oct 25, 2026
- Size
- 14,772 bytes
- Repository stars
- 6,381
- License
- MIT
Guided onboarding wizard for Ouroboros setup.
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
# /ouroboros:setup Guided Ouroboros setup inside a Claude Code session. > Other runtimes (Codex, Copilot, OpenCode, and others) configure through the > CLI instead, for example `ouroboros setup --runtime codex` or > `ouroboros setup --runtime copilot`. See > [Getting Started](https://github.com/Q00/ouroboros/blob/main/docs/getting-started.md). ## Usage ``` ooo setup /ouroboros:setup /ouroboros:setup --uninstall ``` Claude setup confirms the runtime profile (the Claude Agent SDK on MCP 1.x) and optionally adds an Ouroboros reference block to the project's CLAUDE.md. It deliberately leaves `~/.claude/mcp.json` untouched because marketplace plugin wiring owns that file. `[claude]` and its explicit `[claude-sdk]` alias use MCP 1.x. The plugin launches `[mcp]` in a separate MCP 2 process with the dependency-free `[claude-cli]` worker. ## Setup Wizard Flow Ask questions with the active runtime's `ask_user` capability unless a step says otherwise. ### Python Runtime (Required) Define this resolver in the same shell before any snippet below. It accepts only Python 3.12 or newer (`python3`, then `python`, then uv) and preserves …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ju4ii6hw7h6bzcdu/7816f2a7ba4bb133f7e2c7fde5cb96a96f80f41bb3d1067772418e8a66472783.json
Then /plugin install setup@markdownregistry-ju4ii6hw7h6bzcdu in Claude Code. It installs git:20261117.c0a64b7, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add q00/ouroboros/setup@sha256:7816f2a7ba4bb133The line at the top of this page pins the label git:20261117.c0a64b7, 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_ju4ii6hw7h6bzcdu)
2 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 q00/ouroboros/setup 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 setup from somewhere else? Ask it: where did my setup 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 5 versions of this file, between Oct 25, 2026 and Nov 17, 2026, about one every 6 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.c0a64b7 latest | 2026-11-17 | c0a64b7 | 14,772 B | B | view · diff |
| git:20261117.a4d4551 | 2026-11-17 | a4d4551 | 14,772 B | B | view · diff |
| git:20261116.64a2b2e | 2026-11-16 | 64a2b2e | 14,772 B | B | view · diff |
| git:20261113.54dad8e | 2026-11-13 | 54dad8e | 14,703 B | B | view · diff |
| git:20261025.5f5fca9 | 2026-10-25 | 5f5fca9 | 14,703 B | B | 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/setup/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
- fail: No curl or wget piped into a shell (matched: curl -LsSf https://astral.sh/uv/install.sh | sh)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14772 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 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
q00/ouroboros · 6,381 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ju4ii6hw7h6bzcdu GET https://markdownregistry.com/api/v1/resolve?ref=q00/ouroboros/setup GET https://markdownregistry.com/api/v1/blob/7816f2a7ba4bb133f7e2c7fde5cb96a96f80f41bb3d1067772418e8a66472783
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.