bystablyai· 16 skills
Use Orca orchestration for structured multi-agent coordination: threaded messages, blocking ask/reply flows, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, or decomposing work across agents. Use orca-cli instead for full ownership handoffs, including requests phrased as "hand off", "handoff", "handover", "give this to another agent", or "another worktree" when the user did not explicitly ask to supervise, monitor, wait for results, or coordinate a DAG. Use orca-cli for ordinary terminal control, lightweight terminal prompts, shell commands, Orca worktree management, reading or waiting on terminals, and automation of the browser embedded inside Orca. Use Computer Use for browser windows, webviews, Orca app UI, or desktop UI outside Orca's embedded browser.
$npx -y skills add stablyai/orca --skill orchestrationInstalls into the current project.
Run `npx skills use "https://github.com/stablyai/orca" --skill "stablyai/orca/orchestration"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/stablyai/orca" that are relevant to the current task. Run `npx skills add "https://github.com/stablyai/orca"` and select the relevant skills, then follow their instructions.
| 1 | # Orca Orchestration |
| 2 | |
| 3 | This file is a discovery stub, not the usage guide. The full, version-matched Orca |
| 4 | orchestration reference is served by the `orca` binary itself — kept out of this file on |
| 5 | purpose so it can never drift from the binary that will actually run your commands. |
| 6 | |
| 7 | Engage Orca orchestration whenever you need structured multi-agent coordination: threaded |
| 8 | messages, blocking ask/reply flows, task dispatch, worker_done/escalation waits, task DAGs, |
| 9 | decision gates, coordinator loops, or decomposing work across agents. Use the orca-cli skill |
| 10 | instead for full ownership handoffs ("hand off", "handoff", "handover", "give this to |
| 11 | another agent", "another worktree") when the user did not ask to supervise, monitor, wait |
| 12 | for results, or coordinate a DAG — and for ordinary terminal control, shell commands, |
| 13 | worktree management, and the built-in browser. Coordination requires real Orca runtime |
| 14 | state; never substitute a non-Orca subagent tool. |
| 15 | |
| 16 | ## Resolve the CLI for this session |
| 17 | |
| 18 | Choose the executable once and reuse it for every later command: |
| 19 | |
| 20 | - If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this |
| 21 | for managed WSL sessions. |
| 22 | - Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`. |
| 23 | - Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare |
| 24 | `orca` there — outside Orca's terminals it normally resolves to the |
| 25 | GNOME Orca screen reader (`/usr/bin/orca`) and starts speech on the user's machine. |
| 26 | - Otherwise, use `orca`. |
| 27 | |
| 28 | Below, `ORCA` is a placeholder for the executable you resolved. Substitute it before |
| 29 | running anything; do not create a shell variable or run `ORCA` literally. This works the |
| 30 | same way in POSIX shells, PowerShell, and cmd.exe. |
| 31 | |
| 32 | If the selected executable cannot run, report its exact error and stop. Do not fall through |
| 33 | to another executable, which could silently target a different Orca build. |
| 34 | |
| 35 | ## Load the full guide before running Orca commands |
| 36 | |
| 37 | ```text |
| 38 | ORCA skills get orchestration |
| 39 | ``` |
| 40 | |
| 41 | That prints the complete, version-matched guide for the exact binary that will handle your |
| 42 | next commands — task creation and dispatch, injected lifecycle preambles, worker_done |
| 43 | authority, decision gates, and coordinator loops. Read it first, then run the specific |
| 44 | command you need. |
| 45 | |
| 46 | Don't guess subcommands or flags from memory or from a cached copy of this stub. They |
| 47 | change between Orca releases, and this file deliberately no longer lists them. Confirm the |
| 48 | app is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and |
| 49 | prefer `--json` for agent-driven calls. |
| 50 | |
| 51 | ## If an older Orca does not recognize `skills get` |
| 52 | |
| 53 | Use this fallback only when the selected binary explicitly reports that `skills get` is an |
| 54 | unknown command. Another failure is not proof of an older binary; report it rather than |
| 55 | guessing or changing executables. For a confirmed pre-guide binary, use only this bounded, |
| 56 | read-only bootstrap to orient. Do not dead-end and do not invent commands: |
| 57 | |
| 58 | ```text |
| 59 | ORCA status --json |
| 60 | ORCA orchestration task-list --json |
| 61 | ORCA terminal list --json |
| 62 | ``` |
| 63 | |
| 64 | Then tell the user that updating Orca restores the full, version-matched guide via |
| 65 | `ORCA skills get orchestration`. Beyond these commands, ask the user rather than guessing a |
| 66 | command surface this older binary may not support. |