Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
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.
Install AO 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/backend/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/backend/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/backend/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/backend/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/backend/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/backend/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/backend/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 backend/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/backend/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/backend/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/backend/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/backend/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/backend/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/backend/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
- ~1.3k tokens
- SKILL.md length
- 540 words
- Files
- 18
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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.
- Spawning a worker for a new task or issue in an AO workspace
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Listing, restoring or killing agent sessions
- Saving a repetitive command or agent task as a reusable Cue
What it does
ao is a thin CLI over the local AO daemon, and each command's help shows its authoritative flags. The catalog table lists commands with what they do and when to use them: spawn for project workers, orchestrators or standalone workers; session for listing, killing, renaming and restoring; agent for inspecting installed harnesses; pr for merging or resolving review threads; project for registering repos; automation for recurring runs; and cue for saving repetitive tasks.
Others cover orchestrator sessions, a native reviewer for a worker's PR (never spawn a worker just to review), send for directing a live agent, report for persisting checkpoints and blockers, preview for running a session's app or opening a file, browser for inspecting and controlling the session's shared live browser, and start for launching the desktop app. Per-command detail files and a references file hold the specifics.
When your agent uses it
- Spawning a worker for a new task or issue in an AO workspace
- Listing, restoring or killing agent sessions
- Saving a repetitive command or agent task as a reusable Cue
- Verifying a web app through the session's shared browser
Example prompts
- “Spawn a worker for this issue and show me its session.”
- “List all running AO sessions and restore the one that terminated.”
- “Create a Cue for the lint-and-test routine I keep repeating.”
Requirements
- The ao CLI and a running AO daemon
What it can do on your machine
Read from SKILL.md and the folder at commit 42d304d. 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 CLI Catalog loads about 1.3k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 540 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 42d304d, republished under its Apache-2.0 licence (© OrchestratorInc). 540 words, ~1,271 tokens.
Download SKILL.mdSave it as
.claude/skills/using-ao/SKILL.md (or your agent's skills folder). This skill also uses 17 other files; get the full folder from GitHub.- name
- using-ao
- description
- Catalog of the AO (Agent Orchestrator) `ao` CLI: spawning workers, managing sessions and projects, creating reusable Cues, sending messages, controlling the shared browser, previewing pages, and daemon control. Use when using the ao CLI, creating Cues, spawning workers, or managing AO sessions in an AO workspace.
- trigger
- Using the ao CLI in an AO workspace: creating Cues, spawning workers, managing sessions/projects, sending messages, controlling or previewing pages.
AO CLI Catalog
ao is a thin CLI over the local AO daemon. Every command is ao <command> --help for the authoritative flag list.
| Command | What it does | When to use | Details |
|---|---|---|---|
spawn | Spawn a project worker, orchestrator, or projectless standalone worker | Starting a new task or issue | commands/spawn.md |
session | Manage agent sessions (list, kill, rename, restore, etc.) | Inspecting or controlling running/terminated sessions | commands/session.md |
agent | Inspect installed harnesses and launch readiness | Choosing or diagnosing an agent harness | ao agent ls --refresh |
pr | Merge a PR or resolve its review threads | Completing a reviewed change | ao pr merge / ao pr resolve-comments |
project | Register, inspect, configure, or remove projects | Setting up or managing repos AO knows about | commands/project.md |
automation | Manage durable recurring session automations | Creating, editing, disabling, deleting, and inspecting scheduled runs | commands/automation.md |
cue | Create or list reusable project Cues | Saving a repetitive command or agent task at the user's request | commands/cue.md |
orchestrator | List orchestrator sessions | Viewing which sessions are orchestrators | commands/orchestrator.md |
review | Start, list, cancel, or submit AO's native reviewer for a worker's PR (default: this session) | Getting an adversarial review of an AO session's PR; never spawn a worker to review | commands/review.md |
send | Send a message to a running agent session | Correcting or directing a live agent | commands/send.md |
report | Persist a meaningful worker report | Checkpoints, blockers, decisions, outputs, and completion | commands/report.md |
preview | Start a session-owned app or open an exact URL/file | Running and showing the worker's relevant app, Markdown, HTML, PDF, or image | commands/preview.md |
browser | Inspect and control the session's shared live browser | Verifying a web app through snapshots, interactions, waits, screenshots, console, and errors | commands/browser.md |
start | Fetch (if needed) and open the AO desktop app | Launching the app | commands/start.md |
stop | Stop the AO daemon | Shutting down AO | commands/stop.md |
status | Show daemon status | Verifying the daemon is up and healthy | commands/status.md |
doctor | Run local health checks | Diagnosing AO setup problems | commands/doctor.md |
import | Import projects from a legacy AO install | Migrating from the old flat-file store | commands/import.md |
version | Print version information | Checking installed version | - |
completion | Generate shell completion scripts | Setting up tab completion | - |
Show full SKILL.md (198 more words)Show less
Conventions
- Most read commands accept
--jsonfor machine-readable output. -p / --projectscopes session subcommand lookups to one project.- Session and project ids are shown by
ao session lsandao project ls. - To refer to a session in AO Chat or the AO terminal, use the canonical in-app
link
ao://sessions/{project-id}/{session-id}. Read commands/session.md for identity, encoding, and safety rules before constructing one. - When the user asks to save a repeatable task as a Cue, use
ao cue list --jsonto check existing definitions, thenao cue create. An agent Cue stores a reusable instruction; a command Cue stores an exact shell command. This agent-facing command can create and read Cues, but cannot edit or delete them. Direct the user to project settings for changes to existing Cues. --agentis an alias for--harnessonao spawn.- Every command accepts
-h / --helpfor the full flag list. - For frontend launch, preview selection, or artifact handoff, read commands/preview.md before acting. Its static-file, project-runtime, and automatic-handoff rules are load-bearing.
- For page inspection, interaction, or request diagnosis, read commands/browser.md. It defines shared-tab behavior and the opt-in network policy.
Use references.md only when a natural-language request does not map clearly to a command above.
© 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 17 other files in backend/internal/skillassets/using-ao of OrchestratorInc/agent-orchestrator.
- SKILL.md
- commands/automation.md
- commands/browser.md
- commands/cue.md
- commands/doctor.md
- commands/import.md
- commands/orchestrator.md
- commands/preview.md
- commands/project.md
- commands/report.md
- commands/review.md
- commands/send.md
- commands/session.md
- commands/spawn.md
- commands/start.md
- commands/status.md
- commands/stop.md
- references.md
Open the folder on GitHubat commit 42d304d
Compare with similar skills
AO 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 CLI Catalog this skillOrchestratorInc/agent-orchestrator | 13k | — | ~1.3k | 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 Cloud CLI Catalog
OrchestratorInc/agent-orchestrator
Documents the ao CLI for spawning, listing, messaging, and killing worker sessions, and for reporting back to an orchestrator from inside a sandbox.
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 CLI Catalog
What does AO CLI Catalog do?
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. ao is a thin CLI over the local AO daemon, and each command's help shows its authoritative flags. The catalog table lists commands with what they do and when to use them: spawn for project workers, orchestrators or standalone workers; session for listing, killing, renaming and restoring; agent for inspecting installed harnesses; pr for merging or resolving review threads; project for registering repos; automation for recurring runs; and cue for saving repetitive tasks.
When should I use AO CLI Catalog?
AO CLI Catalog fits situations like: spawning a worker for a new task or issue in an AO workspace; listing, restoring or killing agent sessions; saving a repetitive command or agent task as a reusable Cue; verifying a web app through the session's shared browser.
How do I install AO CLI Catalog in Claude Code?
Run `npx skills add OrchestratorInc/agent-orchestrator --skill using-ao -a claude-code`. Or copy the skill folder (backend/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 CLI Catalog in Codex?
Run `npx skills add OrchestratorInc/agent-orchestrator --skill using-ao -a codex`. Or copy the skill folder (backend/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 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 CLI Catalog need to run?
SKILL.md names no scripts, command-line tools or credentials: AO CLI Catalog is instructions for the agent only. Our summary lists: The ao CLI and a running AO daemon.
Does AO 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 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 CLI Catalog use?
AO 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 CLI Catalog use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 CLI Catalog?
Skills that share tags, products or a category with AO 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 CLI Catalog?
OrchestratorInc (a GitHub organization) maintains it in OrchestratorInc/agent-orchestrator, which has 12,881 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 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.