orca-cli
bystablyai· 16 skills
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.
How to install orca-cli?
stablyai/orca/orca-cli
$npx -y skills add stablyai/orca --skill orca-cliInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/stablyai/orca" --skill "stablyai/orca/orca-cli"` 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.
SKILL.md
| 1 | # Orca CLI |
| 2 | |
| 3 | This file is a discovery stub, not the usage guide. The full, version-matched Orca CLI |
| 4 | reference is served by the `orca` binary itself — kept out of this file on purpose so it |
| 5 | can never drift from the binary that will actually run your commands. |
| 6 | |
| 7 | Engage Orca whenever its running editor/runtime is the source of truth: Orca-managed |
| 8 | worktrees, folder contexts, terminals, repos, automations, worktree comments, and the |
| 9 | browser embedded inside the Orca app. Triggers include "$orca-cli", "Orca worktree", |
| 10 | "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", |
| 11 | "full handoff" / "handover" / "give this to another agent", and "control the browser |
| 12 | inside Orca". Use plain shell tools when Orca state does not matter. |
| 13 | |
| 14 | ## Resolve the CLI for this session |
| 15 | |
| 16 | Choose the executable once and reuse it for every later command: |
| 17 | |
| 18 | - If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this |
| 19 | for managed WSL sessions. |
| 20 | - Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`. |
| 21 | - Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare |
| 22 | `orca` there — outside Orca's terminals it normally resolves to the |
| 23 | GNOME Orca screen reader (`/usr/bin/orca`) and starts speech on the user's machine. |
| 24 | - Otherwise, use `orca`. |
| 25 | |
| 26 | Below, `ORCA` is a placeholder for the executable you resolved. Substitute it before |
| 27 | running anything; do not create a shell variable or run `ORCA` literally. This works the |
| 28 | same way in POSIX shells, PowerShell, and cmd.exe. |
| 29 | |
| 30 | If the selected executable cannot run, report its exact error and stop. Do not fall through |
| 31 | to another executable, which could silently target a different Orca build. |
| 32 | |
| 33 | ## Load the full guide before running Orca commands |
| 34 | |
| 35 | ```text |
| 36 | ORCA skills get orca-cli |
| 37 | ``` |
| 38 | |
| 39 | That prints the complete, version-matched guide for the exact binary that will handle your |
| 40 | next commands — worktrees, handoffs, terminals, automations, and the built-in browser. |
| 41 | Read it first, then run the specific command you need. |
| 42 | |
| 43 | Don't guess subcommands or flags from memory or from a cached copy of this stub. They |
| 44 | change between Orca releases, and this file deliberately no longer lists them. Confirm the |
| 45 | app is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and |
| 46 | prefer `--json` for agent-driven calls. |
| 47 | |
| 48 | ## If an older Orca does not recognize `skills get` |
| 49 | |
| 50 | Use this fallback only when the selected binary explicitly reports that `skills get` is an |
| 51 | unknown command. Another failure is not proof of an older binary; report it rather than |
| 52 | guessing or changing executables. For a confirmed pre-guide binary, use only this bounded, |
| 53 | read-only bootstrap to orient. Do not dead-end and do not invent commands: |
| 54 | |
| 55 | ```text |
| 56 | ORCA status --json |
| 57 | ORCA worktree ps --json |
| 58 | ORCA terminal list --json |
| 59 | ``` |
| 60 | |
| 61 | Then tell the user that updating Orca restores the full, version-matched guide via |
| 62 | `ORCA skills get orca-cli`. Beyond these commands, ask the user rather than guessing a |
| 63 | command surface this older binary may not support. |
Related
6 picksType
- handoffCompact the current conversation into a handoff document for another agent to pick up.Jul 2026
- lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing…Jul 2026
- lark-eventLark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM…Jul 2026
- lark-vc-agent飞书视频会议会中能力：用于让应用机器人真实加入或离开正在进行的会议，并读取当前身份可见的会中事件、发送会中文本消息或会中表情。适用于用户询问正在开的会议发生了什么、谁在发言、是否共享内容，或需要发现当前可读的进行中会议 ID。不负责已结束会议搜索、参会人快照、纪要、逐字稿或录制查询，这些使用 lark-vc 技能。Jul 2026
- ask-mattAsk which skill or flow fits your situation. A router over the skills in this repo.Jul 2026
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft…Jul 2026
