Agent skill · software engineering · aiskillstore
orca-cli
Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and the browser embedded inside the Orca app. Use when the user says "$orca-cli", "use orca cli", "Orca worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "terminal send", "full handoff", "handover", "give this to another agent", "another worktree", "Orca browser", or "control the browser inside Orca". Prefer this over raw `git worktree`, ad hoc PTYs, Playwright, or Computer Use when the task touches Orca-managed state. Use Computer Use for browser windows, webviews, or desktop UI outside Orca's embedded browser.
Why this skill is useful
Adds specific commands and workflows for managing Orca worktrees and terminals that the AI wouldn't reliably generate on its own.
What it needs
Requires orca installed locally. About 10k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Orca CLI Use orca when Orca's running editor/runtime is the source of truth. On Linux, use orca-ide wherever this file says orca. Dev builds (pnpm dev): after pnpm build:cli, the dev CLI is exposed as orca-dev (the global shim points at this checkout's wrapper + out/cli). Inside a dev Orca's terminals use orca-dev emulator ... (or ./config/scripts/orca-dev.mjs emulator ... for worktree-local invocation that does not depend on the /usr/local/bin symlink). Plain orca targets any installed production Orca. The app's own agent preambles use orca-dev automatically in dev mode. Use plain shell tools when Orca state does not matter. Start Here If Orca is not running, start it: Prefer --json for agent-driven calls. If the CLI is missing, say so explicitly instead of inspecting source files first. Full Handoffs A full handoff transfers ownership to another agent or worktree, then the original agent stops. Treat requests phrased as "hand off", "handoff", "handover", "give this to another agent", "give this to another worktree", "another agent", or "another worktree" as full handoffs unless the user explicitly asks to supervise, monitor, wait for results, track completion, coordinate a DAG, use decision gates, or manage ask/reply. Do not use orca orchestration task-create, orca orchestration dispatch --inject, or orca orchestration check --wait for full handoffs. task-create is also forbidden because it records coordinator-owned tracking state; if a task row is needed, the user asked for supervised orchestration. Deliver the prompt with worktree/terminal commands, report the created worktree/terminal if useful, and stop monitoring. Independent new-worktree handoff: Use --no-parent and omit --base-branch for independent top-level handoffs unless the user explicitly asks for stacked work, "branch from current", or a specific base. Put any current-branch context in the prompt. Custom Codex model/effort handoff: worktree create --agent codex --prompt ... …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/orca-cli