cao-supervisor-protocols
Supervisor-side orchestration patterns for assign, handoff, and idle inbox delivery in CAO
Install
With your agent
Install OMGSkills skill "awslabs/cli-agent-orchestrator:cao-supervisor-protocols" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/awslabs/cli-agent-orchestrator /tmp/cli-agent-orchestrator && ln -s /tmp/cli-agent-orchestrator/skills/cao-supervisor-protocols ~/.claude/skills/cao-supervisor-protocolsFrom README
CAO Supervisor Protocols Use this skill when supervising worker agents through CLI Agent Orchestrator. This skill covers how supervisors should dispatch work, decide between assign and handoff, and receive worker results without blocking inbox delivery. Core MCP Tools From cao-mcp-server, supervisors orchestrate work with: assign(agentprofile, message) for asynchronous work that returns immediately handoff(agentprofile, message) for synchronous work that blocks until the worker finishes sendmessage(message, receiverid=None) for direct messages — receiverid defaults to the terminal that created yours via handoff/assign answeruserprompt(terminalid, answer) for answering a Hermes worker that reports waitinguseranswer Your own terminal ID is available in the CAOTERMINALID environment variable. CAO appends it to assigned task messages and records it on worker terminals automatically, so you rarely need to handle it yourself.