Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
Documents the ao CLI for spawning, listing, messaging, and killing worker sessions, and for reporting back to an orchestrator from inside a sandbox.
Install AO Cloud CLI Catalog
$ npx skills add OrchestratorInc/agent-orchestrator --skill using-ao -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OrchestratorInc/agent-orchestrator using-ao --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/OrchestratorInc/agent-orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cloud/internal/skillassets/using-ao .claude/skills/using-ao && 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 "using-ao" agent skill from https://github.com/OrchestratorInc/agent-orchestrator/tree/main/cloud/internal/skillassets/using-ao into .claude/skills/using-ao/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ao", 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/OrchestratorInc/agent-orchestrator/tree/main/cloud/internal/skillassets/using-aoType 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 OrchestratorInc/agent-orchestrator --skill using-ao -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OrchestratorInc/agent-orchestrator using-ao --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OrchestratorInc/agent-orchestrator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cloud/internal/skillassets/using-ao .agents/skills/using-ao && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "using-ao" agent skill from https://github.com/OrchestratorInc/agent-orchestrator/tree/main/cloud/internal/skillassets/using-ao into .agents/skills/using-ao/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ao", 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 OrchestratorInc/agent-orchestrator --skill using-ao -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OrchestratorInc/agent-orchestrator using-ao --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OrchestratorInc/agent-orchestrator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cloud/internal/skillassets/using-ao .cursor/skills/using-ao && 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 "using-ao" agent skill from https://github.com/OrchestratorInc/agent-orchestrator/tree/main/cloud/internal/skillassets/using-ao into .cursor/skills/using-ao/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ao", 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/OrchestratorInc/agent-orchestrator.git --path cloud/internal/skillassets/using-ao--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 OrchestratorInc/agent-orchestrator --skill using-ao -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OrchestratorInc/agent-orchestrator using-ao --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OrchestratorInc/agent-orchestrator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cloud/internal/skillassets/using-ao .gemini/skills/using-ao && 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 "using-ao" agent skill from https://github.com/OrchestratorInc/agent-orchestrator/tree/main/cloud/internal/skillassets/using-ao into .gemini/skills/using-ao/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ao", 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 OrchestratorInc/agent-orchestrator using-aoInstalls 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 OrchestratorInc/agent-orchestrator --skill using-ao -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OrchestratorInc/agent-orchestrator.git skills-src && mkdir -p .github/skills && cp -r skills-src/cloud/internal/skillassets/using-ao .github/skills/using-ao && 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 "using-ao" agent skill from https://github.com/OrchestratorInc/agent-orchestrator/tree/main/cloud/internal/skillassets/using-ao into .github/skills/using-ao/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ao", 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 OrchestratorInc/agent-orchestrator --skill using-ao -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OrchestratorInc/agent-orchestrator using-ao --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OrchestratorInc/agent-orchestrator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cloud/internal/skillassets/using-ao .opencode/skills/using-ao && 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 "using-ao" agent skill from https://github.com/OrchestratorInc/agent-orchestrator/tree/main/cloud/internal/skillassets/using-ao into .opencode/skills/using-ao/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ao", 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
using-ao- GitHub stars
- 13k
- Token cost
- ~674 tokens
- SKILL.md length
- 284 words
- Files
- 3
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Documents the ao CLI for spawning, listing, messaging, and killing worker sessions, and for reporting back to an orchestrator from inside a sandbox.
- Coordinating multiple AO worker sessions from an orchestrator
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Checking the status and branch of spawned workers
- Sending a message into a running worker's conversation
What it does
This skill explains that ao inside a cloud sandbox is a thinner client than the desktop CLI, with no session, project, status, preview, or browser commands. It lists spawn, list, send, and kill as orchestrator-only commands, report for a worker talking back to its parent orchestrator, and claim-pr for attaching an existing pull request to any session.
Each session runs in its own isolated sandbox reachable only through these commands, never by ssh or a shared filesystem. List supports a --json flag for machine-readable output and an --all flag to include terminated workers, spawning and messaging are idempotent so a success line is durably accepted even before its effect appears, and pull request handling goes through separate socket helpers rather than ao itself.
When your agent uses it
- Coordinating multiple AO worker sessions from an orchestrator
- Checking the status and branch of spawned workers
- Sending a message into a running worker's conversation
- Reporting results back to a parent orchestrator
Example prompts
- “Spawn three worker sessions to split up this refactor.”
- “List every worker I've spawned and their current status.”
- “Send a message to worker abc123 telling it to rerun the tests.”
- “Claim pull request 482 for this session.”
What it can do on your machine
Read from SKILL.md and the folder at commit 4b60f07. 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
AO Cloud CLI Catalog loads about 674 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 284 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 OrchestratorInc/agent-orchestrator at commit 4b60f07, republished under its Apache-2.0 licence (© OrchestratorInc). 284 words, ~674 tokens.
Download SKILL.mdSave it as
.claude/skills/using-ao/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- using-ao
- description
- Catalog of the AO Cloud `ao` CLI available inside a cloud sandbox: spawning worker sessions, listing them, messaging them, reporting to the orchestrator, killing them, and claiming pull requests. Use when orchestrating or coordinating AO cloud sessions with the ao CLI.
- trigger
- Using the ao CLI inside an AO Cloud sandbox: spawning, listing, messaging, reporting to, or killing sessions, or claiming a PR.
AO Cloud CLI Catalog
ao inside a cloud sandbox is a thin client over the AO control plane. It is a
different, smaller CLI than the desktop ao: there is no ao session,
ao project, ao status, ao preview, or ao browser here. Every command is
ao help for the authoritative list.
| Command | What it does | Who can run it | Details |
|---|---|---|---|
spawn | Create a worker session in its own fresh sandbox | Orchestrators only | commands/orchestration.md |
list (ls, status) | List the workers this orchestrator spawned, with branch, status, and PR facts | Orchestrators only | commands/orchestration.md |
send | Send a message into a worker's conversation | Orchestrators only | commands/orchestration.md |
kill (delete, rm) | Terminate a worker session and its sandbox | Orchestrators only | commands/orchestration.md |
report | Send a message to the orchestrator that spawned this session | Workers with an orchestrator parent | commands/orchestration.md |
claim-pr | Attach an existing pull request to this session | Any session | commands/pull-requests.md |
Conventions
ao list --jsonprints machine-readable output;--allincludes terminated workers (hidden by default).--agentis an alias for--harnessonao spawn.- Session ids are UUIDs shown by
ao list. - Every session runs in its own isolated sandbox. Never try to reach another
session's sandbox directly (no ssh, no shared filesystem); the
aocommands above are the only channel between sessions. - A
sendto a worker whose sandbox is still provisioning is queued by the control plane and delivered when the worker's agent is ready — checkruntimeConnectedinao list --jsonto see whether a worker is live. - Spawning and messaging are idempotent server-side; a command that prints a success line has been durably accepted even if the effect is not visible yet.
- Pull requests and reviews are handled through socket helpers described in
commands/pull-requests.md, not through
ao.
© OrchestratorInc, 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
SKILL.md and 2 other files in cloud/internal/skillassets/using-ao of OrchestratorInc/agent-orchestrator.
- SKILL.md
- commands/orchestration.md
- commands/pull-requests.md
Open the folder on GitHubat commit 4b60f07
Compare with similar skills
AO Cloud CLI Catalog 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 |
|---|---|---|---|---|---|---|
| AO Cloud CLI Catalog this skillOrchestratorInc/agent-orchestrator | 13k | — | ~674 | Automated safety check: Pass | Apache-2.0 | |
| Orca CLIstablyai/orca | 87k | 2 repos | ~593 | Automated safety check: Pass | MIT | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| O2 Review Loopopenobserve/openobserve | 22k | — | ~3.7k | Automated safety check: Pass | AGPL-3.0 | |
| Paseo Committeegetpaseo/paseo | 20k | 1 repos | ~496 | Automated safety check: Pass | Custom licence | |
| Mission Control Agent APIbuilderz-labs/mission-control | 6.3k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
Mission Control Agent API
builderz-labs/mission-control
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.
Paseo Agent Handoff
getpaseo/paseo
Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.
More from OrchestratorInc/agent-orchestrator
AO Desktop App Launcher
OrchestratorInc/agent-orchestrator
Launches, restarts and troubleshoots the real AO Electron desktop app from a checkout, with isolated or real local data and checks for stale processes.
Bug Report Triage
OrchestratorInc/agent-orchestrator
Helps a reporter describe a bug, searches for duplicates and gathers diagnostic evidence kept separate from a short, human-worded issue draft.
AO CLI Catalog
OrchestratorInc/agent-orchestrator
Catalog of the ao command-line tool for Agent Orchestrator: spawning workers, managing sessions and projects, Cues, messages, the shared browser, previews and the daemon.
PR Change-Count Header
OrchestratorInc/agent-orchestrator
Calculates and keeps up to date the required code, test and other change-count header at the top of a pull request description in this repository.
Related
Categories
Questions about AO Cloud CLI Catalog
What does AO Cloud CLI Catalog do?
Documents the ao CLI for spawning, listing, messaging, and killing worker sessions, and for reporting back to an orchestrator from inside a sandbox. This skill explains that ao inside a cloud sandbox is a thinner client than the desktop CLI, with no session, project, status, preview, or browser commands. It lists spawn, list, send, and kill as orchestrator-only commands, report for a worker talking back to its parent orchestrator, and claim-pr for attaching an existing pull request to any session.
When should I use AO Cloud CLI Catalog?
AO Cloud CLI Catalog fits situations like: coordinating multiple AO worker sessions from an orchestrator; checking the status and branch of spawned workers; sending a message into a running worker's conversation; reporting results back to a parent orchestrator.
How do I install AO Cloud CLI Catalog in Claude Code?
Run `npx skills add OrchestratorInc/agent-orchestrator --skill using-ao -a claude-code`. Or copy the skill folder (cloud/internal/skillassets/using-ao in OrchestratorInc/agent-orchestrator) into .claude/skills/using-ao in your project. Claude Code loads it when a task matches its description.
How do I install AO Cloud CLI Catalog in Codex?
Run `npx skills add OrchestratorInc/agent-orchestrator --skill using-ao -a codex`. Or copy the skill folder (cloud/internal/skillassets/using-ao in OrchestratorInc/agent-orchestrator) into .agents/skills/using-ao in your project. Codex loads it when a task matches its description.
Can I use AO Cloud CLI Catalog 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 OrchestratorInc/agent-orchestrator --skill using-ao -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/using-ao, .gemini/skills/using-ao, .github/skills/using-ao and .opencode/skills/using-ao in your project.
What does AO Cloud CLI Catalog need to run?
SKILL.md names no scripts, command-line tools or credentials: AO Cloud CLI Catalog is instructions for the agent only.
Does AO Cloud CLI Catalog 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 AO Cloud CLI Catalog 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 AO Cloud CLI Catalog use?
AO Cloud CLI Catalog 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 AO Cloud CLI Catalog use?
About 674 tokens (SKILL.md is roughly 2.7k 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 AO Cloud CLI Catalog?
Skills that share tags, products or a category with AO Cloud CLI Catalog: Orca CLI (stablyai/orca, 87k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains AO Cloud CLI Catalog?
OrchestratorInc (a GitHub organization) maintains it in OrchestratorInc/agent-orchestrator, which has 12,852 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.
Source: OrchestratorInc/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.