orchestrate SKILL.md skillA
orchestrate from danielc000/loom is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add danielc000/loom/orchestrate@git:20261018.26cc6aaPins git:20261018.26cc6aa in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- danielc000/loom
- Path
packages/daemon/assets/skills/orchestrate/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261018.26cc6aa, committed Oct 18, 2026
- First version recorded
- Sep 26, 2026
- Size
- 123,270 bytes
- Repository stars
- 7
- License
- MIT
The operating doctrine for a Loom lead / orchestrator (manager) session. Load at the start of any orchestrator agent to run the lead-manages-workers loop — plan, decompose, delegate, review, merge, recycle — over the loom-orchestration tools. Your agent prompt supplies the project-specifics; this is the cross-project HOW.
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 — Loom lead doctrine You are the **lead**: you plan, decompose, delegate, review, and control worker lifecycle — you do **not** build. Separate worker sessions write the code/notes; your value is judgment: scoping, decisions, the review gate, and lifecycle control. **Depth-1** — workers cannot spawn workers. This skill is the evergreen HOW. The concrete WHAT — your current objective, the frontier, and the backlog — lives in the project's **vault + board**, not in any prompt; you load it with `/loom-pickup`. Your agent prompt only points you at those sources and names the stable specifics (the gate command, where your living resume doc lives). **Project-specifics live in the project's agent prompts + `CLAUDE.md`, never in a shipped or shared skill.** A skill (this one, `/worker`, `/web-design`, …) ships to end-users' OWN projects, so it must stay generic — it teaches the cross-project HOW and defers to the project for the WHAT. A project's conventions, its gate command, its definition of done, its repo/package paths and build commands: put those in the **agent's base prompt** (or the project's own `CLAUDE.md`), which is where you inject them …
Read the whole file at its exact version.
How to install
mdr add danielc000/loom/orchestrate@sha256:f95f5135615fa840The line at the top of this page pins the label git:20261018.26cc6aa, 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_pk6efkbnmfjgq5r4)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Sep 26, 2026 and Oct 18, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261018.26cc6aa latest | 2026-10-18 | 26cc6aa | 123,270 B | A | view · diff |
| git:20261015.a669666 | 2026-10-15 | a669666 | 121,631 B | A | view · diff |
| git:20261013.04f7aef | 2026-10-13 | 04f7aef | 121,652 B | A | view · diff |
| git:20261006.33755c2 | 2026-10-06 | 33755c2 | 120,608 B | A | view · diff |
| git:20261005.8fc688c | 2026-10-05 | 8fc688c | 120,000 B | A | view · diff |
| git:20260926.1541baf | 2026-09-26 | 1541baf | 119,997 B | A | view |
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 (123270 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
danielc000/loom · 7 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pk6efkbnmfjgq5r4 GET https://markdownregistry.com/api/v1/resolve?ref=danielc000/loom/orchestrate GET https://markdownregistry.com/api/v1/blob/f95f5135615fa840f318421aa0373c05c012dfebe8eed568bd5b2c1f1068fc25
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.