team-protocol skillA
team-protocol is agent-read markdown (skill) from vmobifystudio/app-dev-team: Use whenever one role needs something from another role — a blocker, a spec question, a cross-platform divergence, a handoff, or an escalation. Defines the durable team message ledger, who may talk to whom, the anti-ping-pong guard, and when to escalate to the user instead. Triggers from every agent that would otherwise say "I need X from Y" and stop..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Team protocol
A team is not a set of roles. It is a set of roles plus an agreed way to talk.
Without one, this happens: an IC hits an ambiguity, writes `BLOCKED: needs tech-lead`, and exits.
The orchestrator reads it, spawns `tech-lead` with a paraphrase, gets an answer, paraphrases it
back, and re-spawns the IC from cold. Three context rebuilds, two lossy translations, and the
original question is now a summary of a summary.
## The channel: `docs/team/messages.jsonl`
One append-only event log for the whole team, schema `studio-event-schema/v1`. It works on a vanilla
install, survives an agent dying mid-run, and gives a restarted agent its history back.
`docs/team/messages.md` is the **generated human view** of that log — the same relationship
`docs/31-board.md` has to `docs/31-board-events.jsonl`. **Never hand-edit it.** A hand edit is
overwritten by the next render and is invisible to every rule.
```json
{"id":"MSG-0421","v":1,"ts":"2026-07-29T10:12Z","project":"tipjar","thread":"THR-APP-004",
"ticket":"APP-004","kind":"question","from":"android-developer","to":["tech-lead"],
"priority":"material","blocking":false,"requires_response":true,"expires_after_round":6,
…Read the whole file at its exact version.
How to install
mdr add vmobifystudio/app-dev-team/team-protocol@git:20260806.a08c8fdmdr add vmobifystudio/app-dev-team/team-protocol@sha256:617b80fcc37e4498Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_t3bmqofhron4alkf)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260806.a08c8fd latest | 2026-08-06 | a08c8fd | 25,227 B | A | view · diff |
| git:20260806.ec1ce09 | 2026-08-06 | ec1ce09 | 24,340 B | A | view · diff |
| git:20260804.f8653de | 2026-08-04 | f8653de | 23,858 B | A | view · diff |
| git:20260803.c58329f | 2026-08-03 | c58329f | 23,773 B | A | view · diff |
| git:20260801.bf5b6a4 | 2026-08-01 | bf5b6a4 | 23,696 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 (25227 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
vmobifystudio/app-dev-team · 4 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t3bmqofhron4alkf GET https://markdownregistry.com/api/v1/resolve?ref=vmobifystudio/app-dev-team/team-protocol GET https://markdownregistry.com/api/v1/blob/617b80fcc37e4498418b282d336b4b3f90104ed93a0e00dcf8cc44f728acaa3d
Your agent 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.