agent-teams-playbook SKILL.md skillA
agent-teams-playbook from kimyx0207/kim_service is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kimyx0207/kim_service/agent-teams-playbook@v4.10.0Pins v4.10.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kimyx0207/kim_service
- Path
skills/agent-teams-playbook/SKILL.md- Versions recorded
- 5
- Latest version
- v4.10.0, committed Nov 12, 2026
- First version recorded
- Jul 15, 2026
- Size
- 23,270 bytes
- Repository stars
- 193
- License
- MIT
Cross-runtime playbook for multi-agent collaboration, agent teams, swarm orchestration, parallel task distribution, capability discovery, and quality gates on hosts discovered from their current capabilities; client and model selection remain separate. Use for 多agent、agent协作、agent编排、并行agent、分工协作、拉团队、多代理协作 or complex work needing independent roles and review. Map the six-stage workflow to the active host's actual capabilities; report sequential degradation when parallel agents are unavailable.
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
# Agent Teams 编排手册 可选公司事项协作:收到 `workContext` 时读取 [acceptance 的长期事项合同](references/acceptance.md),将当前 run 关联宿主 Work,分开产出、核验、采用、效果与接手。无 WorkContext 时继续既有入口;宿主拥有业务状态、权限和调度,旧有效决定无需重批。 ## 本能力的验收方法 执行前读取 [method.json](method.json) 中当前 capabilityId 的诊断、决策和逐字段 outputChecks,并读取 [任务验收与完整示例](references/acceptance.md)。按本次能力选择相应规则,不用字段齐全、行数或作者自报代替产物质量。缺少 blocking 证据时保留未验收;既有具体授权与宿主最终决定权不变。 专业引用与工具路线继续按下文渐进读取;[来源记录](PROVENANCE.md) 和 [作者正反例](evals/professional-cases.json) 供评审。当前 Meta Skill 发现不会自动注入 method.json,宿主需按此入口读取;未观察到加载或执行时不得宣称生效。 本 Skill 为调用方提供多 Agent 分工、执行和质量检查建议。宿主协调器负责角色边界、过程与最终交付;在 Meta_Kim 中,Router、跨组件状态机和最终验收仍由 Meta_Kim 负责,本包不接管这些职责。 > **核心理解(铁律)**:Agent Teams 是"并行处理 + 结果汇总"模式,不是扩大单个 agent 的上下文窗口。每个 teammate 是独立的执行单元,拥有独立上下文,可以并行处理大量信息,但最终需要将结果汇总压缩后返回主会话。 ## 跨平台兼容层(新增,不替代原流程) 本 Skill 的完整 6 阶段工作流、按需能力解析、Agent → Skill 委派模式、质量把关和故障处理规则仍然保留。不同宿主的差异只影响"用什么工具执行",不影响"是否执行这些阶段"。下表是已有协议映射示例,不是允许使用的客户端名单。 先读取当前宿主提供的能力与配置,再把下列抽象动作映射到实际可用工具。客户端和模型分别记录:Claude Code 可以通过用户配置使用其他模型,模型名不证明当前客户端。MiniMax code、ZCode、Gemini CLI 等客户端也按现场 schema 与工具返回判断,不因名字已列出就宣称原生支持。不要在非 Claude Code 平台原样承诺 `Task`、`TeamCreate`、`SendMessage` 或 `Skill(...)` 一定存在;也不要因为平台工具名不同而跳过阶段0-5。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_6hxqyeejmzrnrrte/5940d417f824c26c4334c2a3d9d7329d72eead2086a83027c13863dddaf0620f.json
Then /plugin install agent-teams-playbook@markdownregistry-6hxqyeejmzrnrrte in Claude Code. It installs v4.10.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kimyx0207/kim_service/agent-teams-playbook@sha256:5940d417f824c26cThe line at the top of this page pins the label v4.10.0, 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_6hxqyeejmzrnrrte)
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 kimyx0207/kim_service/agent-teams-playbook 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 agent-teams-playbook from somewhere else? Ask it: where did my agent-teams-playbook 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 5 versions of this file, between Jul 15, 2026 and Nov 12, 2026, about one every 30 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v4.10.0 latest | 2026-11-12 | a12723c | 23,270 B | A | view · diff |
| v4.9.1 | 2026-11-11 | e801655 | 21,372 B | A | view · diff |
| v4.9.0 | 2026-11-10 | c4dcec8 | 20,501 B | A | view · diff |
| v4.8.0 | 2026-10-02 | cbb88c8 | 19,299 B | A | view · diff |
| v4.8.0 | 2026-07-15 | cad3517 | 17,164 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/agent-teams-playbook/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 (23270 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
kimyx0207/kim_service · 193 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6hxqyeejmzrnrrte GET https://markdownregistry.com/api/v1/resolve?ref=kimyx0207/kim_service/agent-teams-playbook GET https://markdownregistry.com/api/v1/blob/5940d417f824c26c4334c2a3d9d7329d72eead2086a83027c13863dddaf0620f
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.