collaboration-playbook SKILL.md skillA

collaboration-playbook from hkuds/autoswarm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add hkuds/autoswarm/collaboration-playbook@git:20261020.3598af2

Pins git:20261020.3598af2 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
hkuds/autoswarm
Path
autoswarm-v1.0.0/.opc/skills/collaboration-playbook/SKILL.md
Versions recorded
1
Latest version
git:20261020.3598af2, committed Oct 20, 2026
Size
6,572 bytes
Repository stars
2,651
License
MIT

Standing rules for how any role in an AutoSwarm company coordinates with its peers — work-item discipline, messaging, meetings, and blocking collaboration. Loaded only in company_mode.

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

# Collaboration Playbook

You are one role inside an AutoSwarm company. Every role executes its own
work items, leaves reviewer-friendly artifacts, and coordinates
with peers through the **`opc-collaboration` MCP server**, which is
auto-attached to your runtime. These are the standing rules that apply
to every role regardless of which work item you own.

You are never the whole project. Stay inside your work-item boundary.

## Work Item Discipline

- Own your work item. Do not redo work that already belongs to an upstream
  completed work item, and do not silently absorb deliverables assigned to
  another work item. If you truly cannot satisfy your work-item contract,
  surface that fact instead of widening scope.
- Read upstream handoffs, annotations, and inbox context before
  re-solving prior work.
- Your completion bar is higher than "it works on my turn." Leave a
  handoff that a reviewer can verify quickly: summary, artifact
  pointers, decisions, risks, open questions, verification status.
- Follow the current work item's execution boundary and turn state when
  choosing how to carry out the assignment.

## Messaging (the default path)
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_24sne2f4fp7w6uzb/6228406281bac5c17806ec7fc1002740c4c5667206b54900714db58de60fd496.json

Then /plugin install collaboration-playbook@markdownregistry-24sne2f4fp7w6uzb in Claude Code. It installs git:20261020.3598af2, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add hkuds/autoswarm/collaboration-playbook@sha256:6228406281bac5c1

The line at the top of this page pins the label git:20261020.3598af2, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_24sne2f4fp7w6uzb.svg)](https://markdownregistry.com/a/art_24sne2f4fp7w6uzb)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in hkuds/autoswarm/collaboration-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 collaboration-playbook from somewhere else? Ask it: where did my collaboration-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 1 version of this file, committed on Oct 20, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261020.3598af2 latest2026-10-20 3598af2 6,572 BA view
Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (6572 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

GitHub

hkuds/autoswarm · 2,651 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_24sne2f4fp7w6uzb
GET https://markdownregistry.com/api/v1/resolve?ref=hkuds/autoswarm/collaboration-playbook
GET https://markdownregistry.com/api/v1/blob/6228406281bac5c17806ec7fc1002740c4c5667206b54900714db58de60fd496

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.

More from hkuds/autoswarm

clawhub SKILL.md skill
hkuds/autoswarm · autoswarm-v1.0.0/.opc/skills/clawhub/SKILL.md · Search and install agent skills from ClawHub, the public skill registry. Use when needing new capabilities, searching…
git:20261020.3598af2 · audit A · 2,651 stars
cron SKILL.md skill
hkuds/autoswarm · autoswarm-v1.0.0/.opc/skills/cron/SKILL.md · Schedule reminders, recurring tasks, and one-time jobs using system crontab.
git:20261020.3598af2 · audit A · 2,651 stars
github SKILL.md skill
hkuds/autoswarm · autoswarm-v1.0.0/.opc/skills/github/SKILL.md · Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and…
git:20261020.3598af2 · audit A · 2,651 stars
memory SKILL.md skill
hkuds/autoswarm · autoswarm-v1.0.0/.opc/skills/memory/SKILL.md · Manage durable global/project memory in `.opc/memory/global.md` and `.opc/memory/projects/<current_project_id>.md`.
git:20261020.3598af2 · audit A · 2,651 stars
skill-creator SKILL.md skill
hkuds/autoswarm · autoswarm-v1.0.0/.opc/skills/skill-creator/SKILL.md · Create or update skills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
git:20261020.3598af2 · audit A · 2,651 stars
skill-evolution SKILL.md skill
hkuds/autoswarm · autoswarm-v1.0.0/.opc/skills/skill-evolution/SKILL.md · Evolve new skills from project experience. Use when a repeating pattern, useful workflow, or hard-won knowledge should…
git:20261020.3598af2 · audit A · 2,651 stars
tmux SKILL.md skill
hkuds/autoswarm · autoswarm-v1.0.0/.opc/skills/tmux/SKILL.md · Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
git:20261020.3598af2 · audit A · 2,651 stars
weather SKILL.md skill
hkuds/autoswarm · autoswarm-v1.0.0/.opc/skills/weather/SKILL.md · Get current weather and forecasts (no API key required).
git:20261020.3598af2 · audit A · 2,651 stars
opc-collab SKILL.md skill
hkuds/autoswarm · autoswarm-v1.0.0/opc/skills_assets/opc_collab/SKILL.md · Collaborate with other agents in AutoSwarm company mode via the `opc-collab` CLI — send messages, request user input…
git:20261020.3598af2 · audit A · 2,651 stars

Every file in hkuds/autoswarm

Browse by kind, by grade A, or by owner.