zero-human-dev-team SKILL.md skillA
zero-human-dev-team from 5dive-ai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 5dive-ai/skills/zero-human-dev-team@git:20261019.ef248a5Pins git:20261019.ef248a5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 5dive-ai/skills
- Path
zero-human-dev-team/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261019.ef248a5, committed Oct 19, 2026
- First version recorded
- Oct 19, 2026
- Size
- 19,562 bytes
- Repository stars
- 2
- License
- MIT
Every rule for running a team of AI coding agents that write, review, test and release code, file tasks and message each other and their human. Use when setting up coding agents, deciding who checks whose work, or when an AI dev team keeps breaking things.
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
# Zero human dev team rules We have run a team of AI coding agents on our own product since April 2026. ## Tasks 1. **All work lives on one shared task board.** Each task has one owner. Agents read a task's state from the board, never from memory or chat. 2. **Agents change the board only through its own tool.** A direct write to its database leaves a state the tool can't explain. 3. **One task per agent turn.** A scheduler hands each agent its next task, with a minimum gap between wakes. 4. **Before starting a task, check whether it is already fixed, and whether that fix is released.** A fix that is merged but not released reproduces exactly like an open bug. 5. **Every task ends in one of four states:** done, with a result of one or two sentences that make sense on their own; handed to a reviewer; waiting on a human, with one clear question; or cancelled, because it is irrelevant or impossible. 6. **The tool refuses a blank result on close or cancel.** Never cancel another agent's task without telling it. Why: agents cancelled seven tasks with empty results in three days. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_4c2ildu56tzxhism/58f97c51a55ea451d37b2ffc229684fbc77753c6df9cdb66e41f7f5ef967bbc4.json
Then /plugin install zero-human-dev-team@markdownregistry-4c2ildu56tzxhism in Claude Code. It installs git:20261019.ef248a5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add 5dive-ai/skills/zero-human-dev-team@sha256:58f97c51a55ea451The line at the top of this page pins the label git:20261019.ef248a5, 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_4c2ildu56tzxhism)
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 5dive-ai/skills/zero-human-dev-team 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 zero-human-dev-team from somewhere else? Ask it: where did my zero-human-dev-team 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 2 versions of this file, all committed on Oct 19, 2026.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.ef248a5 latest | 2026-10-19 | ef248a5 | 19,562 B | A | view · diff |
| git:20261019.cdc5dc2 | 2026-10-19 | cdc5dc2 | 18,269 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/zero-human-dev-team/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 (19562 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
5dive-ai/skills · 2 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4c2ildu56tzxhism GET https://markdownregistry.com/api/v1/resolve?ref=5dive-ai/skills/zero-human-dev-team GET https://markdownregistry.com/api/v1/blob/58f97c51a55ea451d37b2ffc229684fbc77753c6df9cdb66e41f7f5ef967bbc4
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.