tagteam SKILL.md skillA
tagteam from smiley73/tagteam is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add smiley73/tagteam/tagteam@git:20261030.867b9baPins git:20261030.867b9ba in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- smiley73/tagteam
- Path
skills/tagteam/SKILL.md- Versions recorded
- 20
- Latest version
- git:20261030.867b9ba, committed Oct 30, 2026
- First version recorded
- Oct 17, 2026
- Size
- 73,651 bytes
- Repository stars
- 4
- License
- MIT
Shared reference for tagteam — configuration, artifact layout, dispatching, the Codex bridge, the Git protocol, the gates and recovery. Read by /tagteam:plan and /tagteam:ship before they do anything.
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
# tagteam reference Tagteam takes a vague goal to merged pull requests. `/tagteam:plan` interviews you until the outcome is concrete, drafts a plan, has it reviewed once by three independent readers whose findings the drafter answers, and expands it into spec files. `/tagteam:ship` implements those specs one at a time, reviews each with a cross-engine panel, and brings each to a merge. Nothing reaches `base` without a person's approval or Merge. A spec that merges straight into `base` — a one-spec plan, or any plan with `planBranch` off — always waits for that approval; it is the approval every such spec needs, not a fault. With `planBranch` on, a plan of two or more specs ships on the familiar feature branch: the branch one feature, here one plan, is collected on before it reaches `base` through a single pull request. Here it is called the plan branch, `plan/<slug>`, and what is particular to it is that tagteam creates it and deletes it, and checks the combined change once before that final pull request. Its specs merge into it without waiting once every gate is satisfied, and the plan's own pull request is the one place a person judges the combined change and says Merge. …
Read the whole file at its exact version.
How to install
mdr add smiley73/tagteam/tagteam@sha256:b57245c4f8a46805The line at the top of this page pins the label git:20261030.867b9ba, 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_xwnhrmhbhmv5qob2)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 20 versions of this file, between Oct 17, 2026 and Oct 30, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261030.867b9ba latest | 2026-10-30 | 867b9ba | 73,651 B | A | view · diff |
| git:20261030.0bdcebb | 2026-10-30 | 0bdcebb | 72,764 B | A | view · diff |
| git:20261030.6911f31 | 2026-10-30 | 6911f31 | 71,919 B | A | view · diff |
| git:20261030.2ad68dd | 2026-10-30 | 2ad68dd | 72,060 B | A | view · diff |
| git:20261030.8839baf | 2026-10-30 | 8839baf | 71,825 B | A | view · diff |
| git:20261024.1e8bdc9 | 2026-10-24 | 1e8bdc9 | 69,029 B | A | view · diff |
| git:20261024.8186d80 | 2026-10-24 | 8186d80 | 68,974 B | A | view · diff |
| git:20261024.f18514a | 2026-10-24 | f18514a | 68,646 B | A | view · diff |
| git:20261024.715a46b | 2026-10-24 | 715a46b | 67,976 B | A | view · diff |
| git:20261024.efe02d2 | 2026-10-24 | efe02d2 | 67,175 B | A | view · diff |
| git:20261020.b94db52 | 2026-10-20 | b94db52 | 55,445 B | A | view · diff |
| git:20261020.e111f5e | 2026-10-20 | e111f5e | 49,628 B | A | view · diff |
| git:20261020.8d53e43 | 2026-10-20 | 8d53e43 | 45,191 B | A | view · diff |
| git:20261020.e03b31c | 2026-10-20 | e03b31c | 43,274 B | A | view · diff |
| git:20261020.5f3a49d | 2026-10-20 | 5f3a49d | 39,616 B | A | view · diff |
| git:20261018.3574ecf | 2026-10-18 | 3574ecf | 35,048 B | A | view · diff |
| git:20261017.3abbb71 | 2026-10-17 | 3abbb71 | 33,523 B | A | view · diff |
| git:20261017.6335a69 | 2026-10-17 | 6335a69 | 32,411 B | A | view · diff |
| git:20261017.74d41a4 | 2026-10-17 | 74d41a4 | 32,689 B | A | view · diff |
| git:20261017.5cbdc55 | 2026-10-17 | 5cbdc55 | 32,434 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 (73651 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
smiley73/tagteam · 4 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xwnhrmhbhmv5qob2 GET https://markdownregistry.com/api/v1/resolve?ref=smiley73/tagteam/tagteam GET https://markdownregistry.com/api/v1/blob/b57245c4f8a46805de7c2124a9cc2d4f768bacf2fb9a00f685dc2bd41998859e
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.