Agent skill · software engineering · stablyai
orchestration
Use Orca orchestration for structured multi-agent coordination: threaded messages, blocking ask/reply flows, task dispatch, worker_done/escalation waits, task DAGs, decision gates, or coordinator loops. 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 terminal control, lightweight terminal prompts, shell commands, Orca worktree management, reading or waiting on terminals, and the Orca embedded browser. Use Computer Use for external browser windows, webviews, Orca app UI, or desktop UI outside Orca's embedded browser only when the task requires OS/window-level control such as focus, menus, dialogs, coordinates, or screenshots. Use `orca-cli` for Orca's embedded pages and a page-automation tool such as Playwright or CDP for external pages.
Why this skill is useful
Adds executable scripts for structured multi-agent coordination and task management that are not available in public documentation.
What it needs
Requires orca installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 39,092 stars on the source repository.
What this skill does
Orca Orchestration This file is a discovery stub, not the usage guide. The full, version-matched Orca orchestration reference is served by the orca binary itself — kept out of this file on purpose so it can never drift from the binary that will actually run your commands. Engage Orca orchestration whenever you need structured multi-agent coordination: threaded messages, blocking ask/reply flows, task dispatch, workerdone/escalation waits, task DAGs, decision gates, coordinator loops, or decomposing work across agents. Use the orca-cli skill instead for full ownership handoffs ("hand off", "handoff", "handover", "give this to another agent", "another worktree") when the user did not ask to supervise, monitor, wait for results, or coordinate a DAG — and for ordinary terminal control, shell commands, worktree management, and the built-in browser. Coordination requires real Orca runtime state; never substitute a non-Orca subagent tool. Resolve the CLI for this session Choose the executable once and reuse it for every later command: If the ORCACLICOMMAND environment variable is set, use its value. Orca exports this for managed WSL sessions. Otherwise, in a dev checkout whose session exposes ORCADEVREPOROOT, use orca-dev. Otherwise, on Linux outside an Orca-managed terminal, use orca-ide. Never run bare orca there — outside Orca's terminals it normally resolves to the GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine. Otherwise, use orca. Below, ORCA is a placeholder for the executable you resolved. Substitute it before running anything; do not create a shell variable or run ORCA literally. This works the same way in POSIX shells, PowerShell, and cmd.exe. If the selected executable cannot run, report its exact error and stop. Do not fall through to another executable, which could silently target a different Orca build. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills stablyai/orchestration