brain-setup SKILL.md skillA
brain-setup from msolecki/developer-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add msolecki/developer-os/brain-setup@git:20261109.9e5d826Pins git:20261109.9e5d826 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- msolecki/developer-os
- Path
plugin/skills/brain-setup/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261109.9e5d826, committed Nov 9, 2026
- First version recorded
- Oct 24, 2026
- Size
- 6,834 bytes
- Repository stars
- 3
- License
- MIT
Create the user's Obsidian knowledge vault from the developer-os template, or connect an existing one by adding only what is missing, then point Claude Code at it after the user approves the diff. Use when the user sets up developer-os, has no `Brain vault:` line yet, or says "set up the vault", "create a vault", "connect my vault", "setup brain".
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
# Brain setup
Template: `${CLAUDE_PLUGIN_ROOT}/vault-template`. If that still reads as a literal `${...}`, the template is `../../vault-template` relative to this skill's base directory. Set `TPL` to that absolute path in every command; the Bash environment does not carry `CLAUDE_PLUGIN_ROOT`.
Config directory: `C="${CLAUDE_CONFIG_DIR:-$HOME/.claude}"`. Edit `$C/CLAUDE.md` and `$C/settings.json` in place (they may be symlinks), never through `mv` or a full rewrite.
## 1. Ask for the path and pick the mode
Ask for the vault's absolute path (expand `~`). Reject a path that holds `'`, `"`, `$`, a backtick, `\` or a newline and ask again; set `V` and `TPL` in single quotes in every command. If `$C/CLAUDE.md` already has a `Brain vault:` line with another path, show it and ask which one to keep. If the user picks the new path, remember the old one for the report.
- Path missing or an empty directory: **new vault**.
- Path non-empty: ask whether to **connect an existing vault**. If not, stop; never copy into a non-empty directory.
## 2a. New vault
```bash
TPL='/abs/path/to/plugin/vault-template'; V='/abs/path/to/vault'
mkdir -p "$V" && cp -R "$TPL/." "$V/"
```
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gk2umyryg6e57is5/6ec538aaabe16b2e26f4f645a459e220dbaa73328d497e79a88ecfdff5fdf50d.json
Then /plugin install brain-setup@markdownregistry-gk2umyryg6e57is5 in Claude Code. It installs git:20261109.9e5d826, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add msolecki/developer-os/brain-setup@sha256:6ec538aaabe16b2eThe line at the top of this page pins the label git:20261109.9e5d826, 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_gk2umyryg6e57is5)
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 msolecki/developer-os/brain-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 brain-setup from somewhere else? Ask it: where did my brain-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 24, 2026 and Nov 9, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261109.9e5d826 latest | 2026-11-09 | 9e5d826 | 6,834 B | A | view · diff |
| git:20261108.1fc28b7 | 2026-11-08 | 1fc28b7 | 6,663 B | A | view · diff |
| git:20261108.a63146c | 2026-11-08 | a63146c | 6,526 B | A | view · diff |
| git:20261026.2a21656 | 2026-10-26 | 2a21656 | 6,612 B | A | view · diff |
| git:20261024.0c5d181 | 2026-10-24 | 0c5d181 | 5,752 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/brain-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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6834 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
msolecki/developer-os · 3 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gk2umyryg6e57is5 GET https://markdownregistry.com/api/v1/resolve?ref=msolecki/developer-os/brain-setup GET https://markdownregistry.com/api/v1/blob/6ec538aaabe16b2e26f4f645a459e220dbaa73328d497e79a88ecfdff5fdf50d
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.