New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Collaboration Playbook

by HKUDS in HKUDS/OpenOPC

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

MITAuto-check passedAgent Workflows

Install Collaboration Playbook

skills CLI
$ npx skills add HKUDS/OpenOPC --skill collaboration-playbook -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HKUDS/OpenOPC collaboration-playbook --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HKUDS/OpenOPC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opc/skills/collaboration-playbook .claude/skills/collaboration-playbook && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
collaboration-playbook
GitHub stars
1.8k
Token cost
~1.6k tokens
SKILL.md length
916 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

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

  • Agent Workflows work in your project
  • SKILL.md covers Work Item Discipline, Messaging (the default path), Meetings (rare, for genuine… and Blocking Collaboration (rare —…, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Collaboration Playbook is an agent skill from HKUDS/OpenOPC. Standing rules for how any role in an OpenOPC company coordinates with its peers — work-item discipline, messaging, meetings, and blocking collaboration. Loaded only in companymode.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: OpenOPC: Build Your Personal AI-Native Company — Self-Built, Self-Run, Self-Grown. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/collaboration-playbook”

What it can do on your machine

Read from SKILL.md and the folder at commit b14e85d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Collaboration Playbook loads about 1.6k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 916 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HKUDS/OpenOPC at commit b14e85d, republished under its MIT licence (© HKUDS). 916 words, ~1,638 tokens.

Download SKILL.mdSave it as .claude/skills/collaboration-playbook/SKILL.md (or your agent's skills folder).
name
collaboration-playbook
description
Standing rules for how any role in an OpenOPC company coordinates with its peers — work-item discipline, messaging, meetings, and blocking collaboration. Loaded only in company_mode.
always
true
modes
company_mode

Collaboration Playbook

You are one role inside an OpenOPC 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)

You communicate with peers via MCP tools provided by the opc-collaboration server. Your identity (OPC_COMMS_FROM) is already injected by OpenOPC for each turn — you never pass from_agent as a tool argument; the server reads it from the environment so you cannot accidentally (or deliberately) impersonate another role.

The collaboration tools
ToolPurpose
send_dm(to_agent, subject, body, blocking=False)Send a direct message to another role.
read_inbox(limit=10, mark_read=True)Read your own unread messages.
reply_message(message_id, body, subject="")Reply to a specific message by id.
broadcast_issue(to_agents, subject, body)Send the same message to multiple roles.
find_and_ask_expert(skill_needed, question, blocking=False)Auto-route a question to whoever has the matching capability.
list_colleagues()Discover which roles are in the company.
start_meeting(topic, participants)Open a multi-party meeting room.
respond_meeting(meeting_id, content)Speak in an open meeting.
read_meeting(meeting_id)Read a meeting transcript.
When to send a message

Send ONLY when one of these is true:

  • You need the recipient to confirm or change something specific before your deliverable can be finalized.
  • You discovered a conflict with a completed upstream work item that you cannot resolve from context.
  • You hold information another role provably needs and will not see otherwise (i.e. it is not already in a handoff or shared artifact).
When NOT to send a message
  • Do NOT send messages to acknowledge, summarize what you just did, or loop people in for visibility. Your handoff file IS the visibility mechanism.
  • Do NOT broadcast status updates. If a peer needs the latest status, they will read the artifacts you left.
  • Do NOT send a message that would duplicate information already in a handoff, annotation, or shared memory entry.
When to reply to a message you received

Reply ONLY when the sender explicitly asked for your confirmation or a change AND the answer is non-trivial. If your reply would be "ack, no changes needed", stay silent — silence is the ack. This rule keeps the team from oscillating on trivial back-and-forth.

Checking your inbox

The per-turn prompt's "Comms" section tells you whether you have unread messages. When it does, call read_inbox first thing to see what arrived. Otherwise you do not need to poll the inbox.

Show full SKILL.md (395 more words)Show less

Meetings (rare, for genuine cross-role decisions)

Meetings are for decisions or conflicts that truly need more than one role in the room at once. A normal work-item handoff is NOT a meeting.

To start a meeting, call start_meeting(topic, participants). The tool returns a meeting_id. To speak, call respond_meeting(meeting_id, content). To read what others have posted, call read_meeting(meeting_id).

If you are already inside an open meeting room, the per-turn prompt will list it under the runtime state block. Wrap up the meeting with a concrete decision summary — an open meeting room with no decision is worse than no meeting at all.

Blocking Collaboration (rare — the 10% case)

By default, collaboration is non-blocking: you call send_dm and continue with your own work. But there are situations where your work item genuinely cannot continue without a peer's reply — an urgent decision, an unresolvable conflict with an upstream work item, or a meeting you must wait on.

In those cases, pass blocking=True to send_dm:

send_dm(to_agent="qa_engineer", subject="...", body="...", blocking=True)

OpenOPC will detect the blocking marker, park your work item in AWAITING_PEER, run the recipient with your message available, then resume your work item once a reply has been written. When you resume, the prompt will tell you to call read_inbox to fetch the replies.

Do NOT use blocking=True for:

  • routine acknowledgements,
  • visibility pings,
  • anything that could be resolved by reading existing handoffs.

Abusing blocking semantics defeats the convergence rule and stalls the whole company. If you are tempted to use it, first ask: "could I finish this turn without the reply, leave the question as an open issue in my handoff, and let the peer respond asynchronously?" If yes, do that instead.

Shared Team Memory

The company has a shared team memory file. Its path is provided in the per-turn prompt under the runtime state block. Write durable shared state there — current conclusions, active risks, decisions, open questions, important constraints. Do NOT use it as a chat log or an activity feed.

What This Playbook Is NOT

  • It is not a per-work-item checklist. Your work-item-specific deliverables, inputs, acceptance criteria, and out-of-scope items come from the per-turn task brief, not from here.
  • It is not a tool reference for non-collaboration tools. The set of tools available to you this turn is declared in the tool surface artifact.
  • It is not an org chart. Who you may directly contact is listed in the per-turn topology section.

© HKUDS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .opc/skills/collaboration-playbook of HKUDS/OpenOPC.

Open the folder on GitHubat commit b14e85d

Compare with similar skills

Collaboration Playbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Collaboration Playbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Collaboration Playbook this skillHKUDS/OpenOPC1.8k—~1.6kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from HKUDS/OpenOPC

  • Skill Creator

    HKUDS/OpenOPC

    Create or update skills. An agent skill from HKUDS/OpenOPC.

    1.8k GitHub stars~980 tokensUpdated 28 days ago
    Auto-check passed

  • Clawhub

    HKUDS/OpenOPC

    Search and install agent skills from ClawHub, the public skill registry.

    1.8k GitHub stars~467 tokensUpdated 28 days ago
    Auto-check passed

  • Skill Evolution

    HKUDS/OpenOPC

    Evolve new skills from project experience. An agent skill from HKUDS/OpenOPC.

    1.8k GitHub stars~641 tokensUpdated 28 days ago
    Auto-check passed

  • Opc Collab

    HKUDS/OpenOPC

    Collaborate with other agents in OpenOPC company mode via the opc-collab CLI — send messages, request user input, delegate work, read the manager board, respond in meetings, propose task adjustments.

    1.8k GitHub stars~3.8k tokensUpdated 28 days ago
    Auto-check passed

  • Cron

    HKUDS/OpenOPC

    Schedule reminders, recurring tasks, and one-time jobs using system crontab.

    1.8k GitHub stars~323 tokensUpdated 28 days ago
    Auto-check passed

  • Memory

    HKUDS/OpenOPC

    Manage durable global/project memory in .opc/memory/global.md and .opc/memory/projects/<currentprojectid.md.

    1.8k GitHub stars~304 tokensUpdated 28 days ago
    Auto-check passed

Categories

Questions about Collaboration Playbook

What does Collaboration Playbook do?

Standing rules for how any role in an OpenOPC company coordinates with its peers — work-item discipline, messaging, meetings, and blocking collaboration. Collaboration Playbook is an agent skill from HKUDS/OpenOPC. Standing rules for how any role in an OpenOPC company coordinates with its peers — work-item discipline, messaging, meetings, and blocking collaboration.

When should I use Collaboration Playbook?

Collaboration Playbook fits situations like: agent Workflows work in your project.

How do I install Collaboration Playbook in Claude Code?

Run `npx skills add HKUDS/OpenOPC --skill collaboration-playbook -a claude-code`. Or copy the skill folder (.opc/skills/collaboration-playbook in HKUDS/OpenOPC) into .claude/skills/collaboration-playbook in your project. Claude Code loads it when a task matches its description.

How do I install Collaboration Playbook in Codex?

Run `npx skills add HKUDS/OpenOPC --skill collaboration-playbook -a codex`. Or copy the skill folder (.opc/skills/collaboration-playbook in HKUDS/OpenOPC) into .agents/skills/collaboration-playbook in your project. Codex loads it when a task matches its description.

Can I use Collaboration Playbook in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HKUDS/OpenOPC --skill collaboration-playbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/collaboration-playbook, .gemini/skills/collaboration-playbook, .github/skills/collaboration-playbook and .opencode/skills/collaboration-playbook in your project.

What does Collaboration Playbook need to run?

SKILL.md names no scripts, command-line tools or credentials: Collaboration Playbook is instructions for the agent only.

Does Collaboration Playbook access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Collaboration Playbook safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Collaboration Playbook use?

Collaboration Playbook is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Collaboration Playbook use?

About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Collaboration Playbook?

Skills that share tags, products or a category with Collaboration Playbook: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Collaboration Playbook?

HKUDS (a GitHub organization) maintains it in HKUDS/OpenOPC, which has 1,824 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 11, 2026.

Source: HKUDS/OpenOPC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.