Agent skill · software engineering · aiskillstore
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, 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.
Why this skill is useful
Adds executable commands for managing multi-agent orchestration and task dispatching that aren't found in public documentation.
What it needs
Requires orca installed locally. About 11k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Orca Inter-Agent Orchestration Orchestration is Orca's structured coordination layer for agent messages, task ownership, dispatch state, and worker completion tracking. Use this skill when coordination state matters. For lightweight terminal prompts or basic worktree/terminal/built-in-browser control, use orca-cli. Tool Boundary If a task says to use Orca orchestration, the coordinator must create Orca runtime state with orca orchestration task-create and orca orchestration dispatch --inject or orca orchestration run. Do not substitute non-Orca subagent tools, generic agent-spawn APIs, or chat-only parallel worker features. Those may create useful workers, but they do not create Orca task/dispatch provenance, injected lifecycle preambles, workerdone authority, or decision gates. Before claiming a worker was orchestrated, verify the task/dispatch exists: If the work was accidentally run outside Orca orchestration, say so plainly. To repair provenance, rerun or revalidate the needed work through a fresh Orca terminal plus injected dispatch; do not retroactively describe the external worker as orchestrated. When To Use Send/reply/ask between agent terminals with persistent messages. Dispatch structured tasks to workers and wait for workerdone or escalation. Track task DAGs with dependencies. Run coordinator loops or decision gates. Do not use orchestration merely because the user says "hand off", "handoff", "handover", "give this to another agent", or asks for another worktree/agent/model/effort. Those are full ownership transfers unless the user explicitly asks to supervise, monitor, wait for worker completion/results, coordinate a DAG, use decision gates, or keep a blocking ask/reply loop. Preconditions orca status --json should show a running runtime. orca must be on PATH (orca-ide on Linux). The orchestration experimental feature must be enabled in Settings > Experimental. orca orchestration commands are RPC calls to the running Orca runtime. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/orchestration--81f922