local-parallel SKILL.md skillA
local-parallel 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/local-parallel@git:20261113.9661a88Pins git:20261113.9661a88 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/local-parallel/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261113.9661a88, committed Nov 13, 2026
- First version recorded
- Oct 22, 2026
- Size
- 6,913 bytes
- Repository stars
- 4
- License
- Apache-2.0
Use when: on one machine (no sandbox, only vibemaestro-sdlc and vibemaestro-brain), the person wants several tasks done in parallel — the main session splits the work into tasks, starts one subagent per task (its own worktree, intake to a draft PR), keeps the queue, relays spec approvals, post-checks each PR and merges it with kit:merge-pr.
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
# local-parallel — several tasks at once on one machine
Local way of working: one machine, `vibemaestro-sdlc` and `vibemaestro-brain`, no sandbox. The main session
talks with the person, briefs each task (what must be true, with how it is checked), decides, post-checks, merges, and edits no file of a task;
each task runs in a subagent started with the Agent tool on `agents.worker_model`, which works from its brief: intake to a
draft PR. One task at a time needs none of this: run the normal flow in the main session.
Read the model before the first start: `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sdlc_config.py" get agents.worker_model` (and
`agents.review_model` for the review); if the read fails, the core's fallback (`--default`) applies.
Before the first PR, check the repo has CI: `kit:merge-pr` (section 4) merges only a PR with at least one green check run on its
head (with `merge.required_checks` unset), so a repo with no CI cannot merge any task. Skill `vibemaestro-sdlc:install-gates` adds one.
## 1. Split and queue
- One task = one intent = one branch = one PR. Tasks that touch the same files, or wait on another's merge, run one after another;
the others run in parallel.
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dmds6txagm6igx2s/a6786b77888ea3c23be005c3ac92d5742a87795a8d86fccfcebbb75a3d5a1541.json
Then /plugin install local-parallel@markdownregistry-dmds6txagm6igx2s in Claude Code. It installs git:20261113.9661a88, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vibemaestro/vibemaestro-kit/local-parallel@sha256:a6786b77888ea3c2The line at the top of this page pins the label git:20261113.9661a88, 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_dmds6txagm6igx2s)
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/local-parallel 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 local-parallel from somewhere else? Ask it: where did my local-parallel 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 4 versions of this file, between Oct 22, 2026 and Nov 13, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.9661a88 latest | 2026-11-13 | 9661a88 | 6,913 B | A | view · diff |
| git:20261103.f4a254c | 2026-11-03 | f4a254c | 6,885 B | A | view · diff |
| git:20261031.04472f5 | 2026-10-31 | 04472f5 | 6,966 B | A | view · diff |
| git:20261022.867b0e0 | 2026-10-22 | 867b0e0 | 5,044 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/local-parallel/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 (6913 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_dmds6txagm6igx2s GET https://markdownregistry.com/api/v1/resolve?ref=vibemaestro/vibemaestro-kit/local-parallel GET https://markdownregistry.com/api/v1/blob/a6786b77888ea3c23be005c3ac92d5742a87795a8d86fccfcebbb75a3d5a1541
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.