worker SKILL.md skillA
worker 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/worker@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/worker/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261018.26cc6aa, committed Oct 18, 2026
- First version recorded
- Sep 23, 2026
- Size
- 59,722 bytes
- Repository stars
- 7
- License
- MIT
The operating doctrine for a Loom worker session — a session dispatched by a manager to implement ONE assigned task on an isolated worktree branch. Load at the start of any worker (Dev / Bugfix / Deep-Dive / etc.) agent. Your agent prompt and kickoff supply the task and its 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
# Worker — Loom worker doctrine You implement **one** assigned task — the one named in your kickoff / board task — on your own git worktree branch, and report up when done or blocked. You are a **worker**: your single channel up is `worker_report`, and it reaches your **manager**, never the human. **Depth-1** — you do not spawn workers of your own. **If you use Agent sub-agents, they inherit your FULL MCP tool surface and run in-process** — a sub-agent's `worker_report` / `memory_write` / board write carries your identity and is just as durable as your own. Loom can SOMETIMES tell a sub-agent's call apart from your own and label it for your manager — but only when the correlation is clean: one candidate call, caught within a short window right after it fires. It reads exactly like your own top-level turn whenever more than one such call is in flight at once, the window has already lapsed, the tool isn't one Loom correlates this way at all, or — rarely — a genuine top-level call of yours happens to land inside a live sub-agent's own window and gets mislabeled the other way. **A missing label is never proof a call was yours — don't lean on the label as …
Read the whole file at its exact version.
How to install
mdr add danielc000/loom/worker@sha256:a3d26a9ab54ad7e0The 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_35t325hsfvuyobtb)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Sep 23, 2026 and Oct 18, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261018.26cc6aa latest | 2026-10-18 | 26cc6aa | 59,722 B | A | view · diff |
| git:20261015.a42ff21 | 2026-10-15 | a42ff21 | 57,442 B | A | view · diff |
| git:20260925.e146c80 | 2026-09-25 | e146c80 | 57,194 B | A | view · diff |
| git:20260923.0cf4589 | 2026-09-23 | 0cf4589 | 57,099 B | A | view · diff |
| git:20260923.96044d6 | 2026-09-23 | 96044d6 | 56,864 B | A | view · diff |
| git:20260923.0c80af5 | 2026-09-23 | 0c80af5 | 56,281 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 (59722 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_35t325hsfvuyobtb GET https://markdownregistry.com/api/v1/resolve?ref=danielc000/loom/worker GET https://markdownregistry.com/api/v1/blob/a3d26a9ab54ad7e08c51e19ddacaa3693748700faeb7f3f28efad22529afc29b
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.