agtx One-Shot Project Runner
fynnfluegge/agtx
Runs a whole project unattended on an agtx kanban board, decomposing the goal, starting tasks, unblocking workers and merging each result.
Supervisor-side orchestration patterns for assign, handoff, and idle inbox delivery in CAO
Install Cao Supervisor Protocols
$ npx skills add awslabs/cli-agent-orchestrator --skill cao-supervisor-protocols -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install awslabs/cli-agent-orchestrator cao-supervisor-protocols --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/awslabs/cli-agent-orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cao-supervisor-protocols .claude/skills/cao-supervisor-protocols && rm -rf skills-srcUse ~/.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/
Install the "cao-supervisor-protocols" agent skill from https://github.com/awslabs/cli-agent-orchestrator/tree/main/skills/cao-supervisor-protocols into .claude/skills/cao-supervisor-protocols/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cao-supervisor-protocols", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/awslabs/cli-agent-orchestrator/tree/main/skills/cao-supervisor-protocolsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add awslabs/cli-agent-orchestrator --skill cao-supervisor-protocols -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install awslabs/cli-agent-orchestrator cao-supervisor-protocols --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awslabs/cli-agent-orchestrator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cao-supervisor-protocols .agents/skills/cao-supervisor-protocols && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cao-supervisor-protocols" agent skill from https://github.com/awslabs/cli-agent-orchestrator/tree/main/skills/cao-supervisor-protocols into .agents/skills/cao-supervisor-protocols/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cao-supervisor-protocols", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add awslabs/cli-agent-orchestrator --skill cao-supervisor-protocols -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install awslabs/cli-agent-orchestrator cao-supervisor-protocols --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awslabs/cli-agent-orchestrator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cao-supervisor-protocols .cursor/skills/cao-supervisor-protocols && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cao-supervisor-protocols" agent skill from https://github.com/awslabs/cli-agent-orchestrator/tree/main/skills/cao-supervisor-protocols into .cursor/skills/cao-supervisor-protocols/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cao-supervisor-protocols", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/awslabs/cli-agent-orchestrator.git --path skills/cao-supervisor-protocols--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add awslabs/cli-agent-orchestrator --skill cao-supervisor-protocols -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install awslabs/cli-agent-orchestrator cao-supervisor-protocols --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awslabs/cli-agent-orchestrator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cao-supervisor-protocols .gemini/skills/cao-supervisor-protocols && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cao-supervisor-protocols" agent skill from https://github.com/awslabs/cli-agent-orchestrator/tree/main/skills/cao-supervisor-protocols into .gemini/skills/cao-supervisor-protocols/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cao-supervisor-protocols", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install awslabs/cli-agent-orchestrator cao-supervisor-protocolsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add awslabs/cli-agent-orchestrator --skill cao-supervisor-protocols -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/awslabs/cli-agent-orchestrator.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cao-supervisor-protocols .github/skills/cao-supervisor-protocols && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cao-supervisor-protocols" agent skill from https://github.com/awslabs/cli-agent-orchestrator/tree/main/skills/cao-supervisor-protocols into .github/skills/cao-supervisor-protocols/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cao-supervisor-protocols", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add awslabs/cli-agent-orchestrator --skill cao-supervisor-protocols -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install awslabs/cli-agent-orchestrator cao-supervisor-protocols --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awslabs/cli-agent-orchestrator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cao-supervisor-protocols .opencode/skills/cao-supervisor-protocols && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cao-supervisor-protocols" agent skill from https://github.com/awslabs/cli-agent-orchestrator/tree/main/skills/cao-supervisor-protocols into .opencode/skills/cao-supervisor-protocols/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cao-supervisor-protocols", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cao-supervisor-protocols- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 651 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Supervisor-side orchestration patterns for assign, handoff, and idle inbox delivery in CAO
- Works in 4 steps: Dispatch asynchronous workers with… → Use handoff only for steps that must… → End the turn so asynchronous worker… → …
- Tasks that involve Email management
- SKILL.md covers Core MCP Tools, Choosing Between Assign and…, Idle-Based Message Delivery and Callback Pattern, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Cao Supervisor Protocols is an agent skill from awslabs/cli-agent-orchestrator, published by the product's own GitHub organization. Supervisor-side orchestration patterns for assign, handoff, and idle inbox delivery in CAO
Its SKILL.md is about 1.2k 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, covering Email management and Multi-agent orchestration. It works with Model Context Protocol. The repository describes itself as: Multi-agent orchestration for AI coding CLIs — Claude Code, Kiro, Codex, and more, coordinated in isolated tmux sessions. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Email management
- Tasks that involve Multi-agent orchestration
Example prompts
- “/cao-supervisor-protocols”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Dispatch asynchronous workers with assign — callback routing is automatic (your terminal ID is appended to the message and recorded as the…
- Use handoff only for steps that must finish before you can continue.
- End the turn so asynchronous worker messages can be delivered.
- When messages arrive, synthesize the results and continue the workflow.
What it can do on your machine
Read from SKILL.md and the folder at commit b29f40a. 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
Cao Supervisor Protocols loads about 1.2k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 651 words of instructions outside code blocks.
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 awslabs/cli-agent-orchestrator at commit b29f40a, republished under its Apache-2.0 licence (© awslabs). 651 words, ~1,219 tokens.
Download SKILL.mdSave it as
.claude/skills/cao-supervisor-protocols/SKILL.md (or your agent's skills folder).- name
- cao-supervisor-protocols
- description
- Supervisor-side orchestration patterns for assign, handoff, and idle inbox delivery in CAO
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(agent_profile, message)for asynchronous work that returns immediatelyhandoff(agent_profile, message)for synchronous work that blocks until the worker finishessend_message(message, receiver_id=None)for direct messages —receiver_iddefaults to the terminal that created yours via handoff/assignanswer_user_prompt(terminal_id, answer)for answering a Hermes worker that reportswaiting_user_answer
Your own terminal ID is available in the CAO_TERMINAL_ID environment variable. CAO appends it to assigned task messages and records it on worker terminals automatically, so you rarely need to handle it yourself.
Choosing Between Assign and Handoff
Use assign when the worker should continue independently and report back later. This is the normal pattern for fan-out work or parallel execution.
Use handoff when the next step is blocked on the worker result. The orchestrator waits for completion, captures the worker output, and returns it directly to the supervisor.
Typical pattern:
- Use
assignfor analysis, research, or code changes that can run in parallel. - Use
handofffor report generation, blocking review steps, or any task where you need the result before you can continue.
Idle-Based Message Delivery
Assigned workers usually return results through send_message. Those inbox messages are delivered to the supervisor automatically when the supervisor terminal becomes idle.
This means supervisors should:
- Dispatch all planned worker tasks first
- Finish the turn after dispatching work
- Avoid running placeholder shell commands just to wait
Do not keep the terminal busy with sleep, echo, or similar commands while waiting. A busy terminal delays inbox delivery.
If you need multiple worker results, dispatch them all first, then end the turn. Do not poll manually in a loop.
Callback Pattern
By default, CAO appends your terminal ID and callback instructions to every assigned message automatically, and records your terminal as the worker's caller — workers can reply with send_message without a receiver_id. You do not need to hand-write callback instructions.
You may still include an explicit callback ID in the task message for emphasis:
Analyze dataset A. Send results back to terminal abc123 using send_message.If your deployment disables the automatic suffix (CAO_ENABLE_SENDER_ID_INJECTION=false), the explicit pattern above is required: the structural caller record still works, but the worker gets no in-message reminder.
Show full SKILL.md (267 more words)Show less
Direct Supervisor Communication
Use send_message when you need to contact an existing terminal directly rather than spawning a new worker.
Examples:
- Relay follow-up instructions to a worker you already created.
- Forward a worker result to another coordinator terminal.
- Send a concise status update to a collaborating supervisor.
When sending direct messages, include enough context that the receiver can act without re-reading the full original task.
Interactive Worker Prompts
Hermes workers can stop on approval prompts or clarify pickers and report waiting_user_answer. When a Hermes worker is in that state, do not use assign, handoff, or send_message to answer it. Use answer_user_prompt(terminal_id, answer) with the exact selection or text to submit, such as 1, o, or a custom answer.
Other providers may still emit prompts in their terminal output without reporting waiting_user_answer. For those providers, treat the prompt as ordinary terminal output and answer it with send_message or direct input according to the workflow you are running.
Practical Workflow
- Dispatch asynchronous workers with
assign— callback routing is automatic (your terminal ID is appended to the message and recorded as the worker's caller). - Use
handoffonly for steps that must finish before you can continue. - End the turn so asynchronous worker messages can be delivered.
- When messages arrive, synthesize the results and continue the workflow.
Reliability Guidelines
- Tell workers exactly what deliverable they should return.
- When workers create files, ask them to return absolute paths in their callback message.
- Do not assume results will be delivered while your terminal is still busy.
- Keep orchestration instructions separate from domain requirements so workers can parse both cleanly.
© awslabs, Apache-2.0. 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 skills/cao-supervisor-protocols of awslabs/cli-agent-orchestrator.
Open the folder on GitHubat commit b29f40a
Compare with similar skills
Cao Supervisor Protocols 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cao Supervisor Protocols this skillawslabs/cli-agent-orchestrator | 1.4k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| agtx One-Shot Project Runnerfynnfluegge/agtx | 1.7k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Using Agent RelayAgentWorkforce/relay | 866 | 1 repos | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Basemind CommsGoldziher/basemind | 106 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Bootstrap Google Toolsgoogle/adk-recipes | 10k | — | ~5k | Automated safety check: Warn | Apache-2.0 | |
| Orchestratehashgraph-online/awesome-codex-plugins | 1.2k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Using Agent Relay
AgentWorkforce/relay
A skill your agent uses when you are a registered relay agent (a spawned worker, or a lead that called registeragent) coordinating with peers in real time over current Agent Relay MCP tools -…
Basemind Comms
Goldziher/basemind
Coordinate with other agents working the same repo via basemind's broker — scoped threads, a per-agent inbox, and two-tier messages.
- Official
Bootstrap Google Tools
google/adk-recipes
Install/auth CLIs the sandbox lacks - gws (Drive, Gmail, Sheets, Calendar), gcloud, agents-cli, mcp-cli (MCP servers).
Orchestrate
hashgraph-online/awesome-codex-plugins
Trigger: active multi-agent run. An agent skill from hashgraph-online/awesome-codex-plugins.
Codex with ChatGPT Planning Loop
XiaoDuoYa/codex-with-chatgpt
Uses ChatGPT in the browser as the planning and review brain for a Codex session, with Codex keeping all execution and ChatGPT reading the workspace through a bridge.
More from awslabs/cli-agent-orchestrator
All 14 skills in this repo- Official
Cao MCP Apps
awslabs/cli-agent-orchestrator
Enable, operate, and extend CAO's MCP Apps surface — the host-rendered fleet dashboard visible inside MCP App hosts (Claude Desktop, ChatGPT, VS Code Copilot, Goose, Postman).
- Official
Agui Author
awslabs/cli-agent-orchestrator
Author live dashboard UI from an agent via the emitui MCP tool.
- Official
MCP Apps Builder
awslabs/cli-agent-orchestrator
Load the official MCP Apps builder skills (create-mcp-app, migrate-oai-app, add-app-to-server, convert-web-app) from github.com/modelcontextprotocol/ext-apps.
- Official
Cao Plugin
awslabs/cli-agent-orchestrator
Create a new CAO (CLI Agent Orchestrator) plugin. An agent skill from awslabs/cli-agent-orchestrator.
- Official
Cao Provider
awslabs/cli-agent-orchestrator
Create a new CLI agent provider for CAO (CLI Agent Orchestrator).
- Official
Cao Agent Routing
awslabs/cli-agent-orchestrator
Find and select the best installed CAO agent profile for a task before delegating with assign or handoff.
Related
Works with
Categories
Questions about Cao Supervisor Protocols
What does Cao Supervisor Protocols do?
Supervisor-side orchestration patterns for assign, handoff, and idle inbox delivery in CAO. Cao Supervisor Protocols is an agent skill from awslabs/cli-agent-orchestrator, published by the product's own GitHub organization.
When should I use Cao Supervisor Protocols?
Cao Supervisor Protocols fits situations like: tasks that involve Email management; tasks that involve Multi-agent orchestration.
How do I install Cao Supervisor Protocols in Claude Code?
Run `npx skills add awslabs/cli-agent-orchestrator --skill cao-supervisor-protocols -a claude-code`. Or copy the skill folder (skills/cao-supervisor-protocols in awslabs/cli-agent-orchestrator) into .claude/skills/cao-supervisor-protocols in your project. Claude Code loads it when a task matches its description.
How do I install Cao Supervisor Protocols in Codex?
Run `npx skills add awslabs/cli-agent-orchestrator --skill cao-supervisor-protocols -a codex`. Or copy the skill folder (skills/cao-supervisor-protocols in awslabs/cli-agent-orchestrator) into .agents/skills/cao-supervisor-protocols in your project. Codex loads it when a task matches its description.
Can I use Cao Supervisor Protocols 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 awslabs/cli-agent-orchestrator --skill cao-supervisor-protocols -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cao-supervisor-protocols, .gemini/skills/cao-supervisor-protocols, .github/skills/cao-supervisor-protocols and .opencode/skills/cao-supervisor-protocols in your project.
What does Cao Supervisor Protocols need to run?
SKILL.md names no scripts, command-line tools or credentials: Cao Supervisor Protocols is instructions for the agent only.
Does Cao Supervisor Protocols 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 Cao Supervisor Protocols 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 Cao Supervisor Protocols use?
Cao Supervisor Protocols is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cao Supervisor Protocols use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Cao Supervisor Protocols?
Skills that share tags, products or a category with Cao Supervisor Protocols: agtx One-Shot Project Runner (fynnfluegge/agtx, 1.7k stars), Using Agent Relay (AgentWorkforce/relay, 866 stars), Basemind Comms (Goldziher/basemind, 106 stars) and Bootstrap Google Tools (google/adk-recipes, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cao Supervisor Protocols?
awslabs (a GitHub organization, an official publisher) maintains it in awslabs/cli-agent-orchestrator, which has 1,396 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 8, 2026.
Source: awslabs/cli-agent-orchestrator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.