stablyai / orca

orca-cli is the core one: worktrees, terminals, artifacts, and skill-sharing all go through the orca command. computer-use adds OS-level control of visible windows outside Orca's own embedded browser; orca-emulator and orca-emulator-android drive a booted iOS Simulator or Android device from inside Orca's emulator pane; orchestration coordinates multiple supervised Orca workers with task DAGs and decision gates; and orca-per-workspace-env sets up the disposable cloud, VM, or SSH environment a workspace runs in. Each skill's own description tells an agent which of the others to reach for instead in a neighboring case — computer-use for external windows, orca-cli for Orca's own embedded pages, a page-automation tool for anything outside Orca entirely.

Two of the eight are the same skill: linear-tickets' own description calls itself the legacy bundled name for orca-linear, kept only so existing installs still resolve. Install both and you get one Linear-ticket capability twice, not two — seven distinct skills is the real count, and every one of them does nothing against a plain git checkout or a CI runner that does not have Orca installed.

READ THE FULL ANALYSIS＋

Installing this means downloading a compiled app, not cloning a repository. The README's own install path is a download page and the iOS and Android app stores, not npm install or pip install — the source on GitHub is MIT-licensed, but these eight skills exist to drive the packaged desktop application, not to be read and reused against Orca's own source tree.

Who this is for. Someone who already runs Orca to fan a task across several coding agents in parallel worktrees, and wants those same agents scripting Orca itself — spawning a child worktree, waiting on a terminal, filing the Linear ticket a task came from — rather than someone looking for a Computer Use skill to point at any desktop app; the computer-use skill here is explicitly scoped to windows outside Orca, and orca-cli explicitly owns everything inside it.