bootstrap SKILL.md skillA
bootstrap from vibemaestro/vibemaestro-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vibemaestro/vibemaestro-kit/bootstrap@git:20261103.f4a254cPins git:20261103.f4a254c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vibemaestro/vibemaestro-kit
- Path
plugins/vibemaestro-sdlc/skills/bootstrap/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261103.f4a254c, committed Nov 3, 2026
- Size
- 4,412 bytes
- Repository stars
- 4
- License
- Apache-2.0
Use when: a session starts on a new or moved machine, there is no baton launcher yet, or SessionStart says the baton permission check failed. One owner-signed kit run (kit:bootstrap) installs the launcher and adds the permission block (with attribution off where a key is absent) to the user settings, after a machine report; then the session post-checks and does the follow-up steps the report's plugins name.
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
# bootstrap: set up BatonRun on a machine in one run
The setup is one kit run, `kit:bootstrap`. Its rules (check, rehearse, sign, run, post-check, undo, the decision
card, the modes) are BatonRun's: the standard is `docs/batonrun.md` in the plugin root, the operating instructions are the
skill `batonrun`. This file adds only what is particular to the bootstrap.
## What the run does
- **Report.** `CHECK` lines: the sdlc version running and installed, the launcher, the rules in force, the mode,
attribution, `gh auth status`. Each installed plugin that depends on this one and ships `scripts/bootstrap_report.py` adds
its own lines: what that plugin needs on this machine, and where its follow-up steps are written.
- **At most two writes.** It installs the launcher, then merges the printed block into the user settings through the kind
`settings-merge`. The kind adds rules and absent attribution keys, and removes and flips nothing; a missing settings file
is created as `{}` first.
- **Header.** `Stops: security-boundary`: it adds allow rules, so the owner signs, in every mode.
- **Undo.** It puts each file back byte for byte while it is what the run left.
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_pfuzxjtkhdzubpls/1a19407be3181b6dda86ac0f21d9c01adb74189f9609354b403a98f89898638d.json
Then /plugin install bootstrap@markdownregistry-pfuzxjtkhdzubpls in Claude Code. It installs git:20261103.f4a254c, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vibemaestro/vibemaestro-kit/bootstrap@sha256:1a19407be3181b6dThe line at the top of this page pins the label git:20261103.f4a254c, 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_pfuzxjtkhdzubpls)
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 vibemaestro/vibemaestro-kit/bootstrap 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 bootstrap from somewhere else? Ask it: where did my bootstrap 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 Nov 3, 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/bootstrap/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 (4412 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
vibemaestro/vibemaestro-kit · 4 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pfuzxjtkhdzubpls GET https://markdownregistry.com/api/v1/resolve?ref=vibemaestro/vibemaestro-kit/bootstrap GET https://markdownregistry.com/api/v1/blob/1a19407be3181b6dda86ac0f21d9c01adb74189f9609354b403a98f89898638d
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 vibemaestro/vibemaestro-kit
Every file in vibemaestro/vibemaestro-kit