orchestrate SKILL.md skillA
orchestrate from peterpme/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add peterpme/skills/orchestrate@git:20261112.23a42a5Pins git:20261112.23a42a5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- peterpme/skills
- Path
orchestrate/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261112.23a42a5, committed Nov 12, 2026
- First version recorded
- Nov 11, 2026
- Size
- 13,983 bytes
- Repository stars
- 28
- License
- none declared
Use when Peter asks you to build, fix, migrate or refactor something that ends in a PR and spans more than one file ("build X and get me a pr", a ticket with acceptance criteria, a migration, a new project), a multi-PR program, or when you coordinate several workers. Writes the contract first. Not for a one-file fix or a one-off investigation (delegate).
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
# Orchestrate Peter's goal: ask once, get finished PRs. Every time he has to say "no", "I said", "status?" or "resolve the comments", the work failed even if the code is right. | Task size | Do | |---|---| | Small fix, one file, obvious proof | The Finish steps in global AGENTS.md only | | One PR | Contract (step 1), build, diff review, gate | | Several PRs or several workers | All steps, and you only orchestrate | ## 1. Write the contract before any code Post it on the ticket, which is the source, and keep a working copy at `.verification/<task>/CONTRACT.md` in the worktree for briefs, reviews and reports to point at. Re-read it after `/compact` or a resume, before acting. On a program with several workers, keep your context for decisions: have a read-only worker do the repo investigation and draft the contract from Peter's words, then check the draft against his request and decide. 1. **Goal.** Peter's request, quoted word for word, then one sentence on the outcome he will see. 2. **Decisions.** Every choice already made, each with its source. Look in this order and record what you find: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dzkmkanjd3soq7gx/ef903fef44193502d462ad81f73090b15457d911bec14c36290ce915550bf87d.json
Then /plugin install orchestrate@markdownregistry-dzkmkanjd3soq7gx in Claude Code. It installs git:20261112.23a42a5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add peterpme/skills/orchestrate@sha256:ef903fef44193502The line at the top of this page pins the label git:20261112.23a42a5, 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_dzkmkanjd3soq7gx)
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 peterpme/skills/orchestrate 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 orchestrate from somewhere else? Ask it: where did my orchestrate 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 6 versions of this file, between Nov 11, 2026 and Nov 12, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261112.23a42a5 latest | 2026-11-12 | 23a42a5 | 13,983 B | A | view · diff |
| git:20261112.4dccf65 | 2026-11-12 | 4dccf65 | 14,298 B | A | view · diff |
| git:20261111.fb4a9f9 | 2026-11-11 | fb4a9f9 | 14,288 B | A | view · diff |
| git:20261111.a692f0d | 2026-11-11 | a692f0d | 14,447 B | A | view · diff |
| git:20261111.724ce32 | 2026-11-11 | 724ce32 | 14,405 B | A | view · diff |
| git:20261111.f660fb7 | 2026-11-11 | f660fb7 | 14,132 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/orchestrate/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 (13983 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
peterpme/skills · 28 stars · license none declared · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dzkmkanjd3soq7gx GET https://markdownregistry.com/api/v1/resolve?ref=peterpme/skills/orchestrate GET https://markdownregistry.com/api/v1/blob/ef903fef44193502d462ad81f73090b15457d911bec14c36290ce915550bf87d
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.