orca-cli
/orca-cli
Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, 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", "orca artifacts", "share HTML/Markdown", "public artifact link", or "control the browser inside Orca". Prefer this over raw `git worktr
- Author
- HK-hub ↗
- Repository
- AgentSkills ↗
- Licence
- MIT
- Last repository change
- 18.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, 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", "orca artifacts", "share HTML/Markdown", "public artifact link", or "control the browser inside Orca". Prefer this over raw `git worktr
Triggers from the description
Original author description
Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, 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", "orca artifacts", "share HTML/Markdown", "public artifact link", or "control the browser inside Orca". Prefer this over raw `git worktr
How it works
- Resolve the CLI for this session
- Load the full guide before running Orca commands
- If an older Orca does not recognize skills get
SKILL.md preview
--- name: orca-cli description: >- Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, 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", "orca artifacts", "share HTML/Markdown", "public artifact link", 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. --- # Orca CLI This file is a discovery stub, not the usage guide. The full, version-matched Orca CLI 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 whenever its running editor/runtime is the source of truth: Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and the browser embedded inside the Orca app. Triggers include "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "full handoff" / "handover" / "give this to another agent", and "control the browser inside Orca". Use plain shell tools when Orca state does not matter. ## Resolve the CLI for this session Choose the executable once and reuse it for every later command: - If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this for managed WSL sessions. - Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, 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. ## Load the full guide before running Orca commands ```text ORCA skills get orca-cli ``` That prints the complete, version-matched guide for the exact binary that will handle your next commands — worktrees, handoffs, terminals, automations, and the built-in browser. Read it first, then run the specific command you need. Don't guess subcommands or flags from memory or from a cached copy of this stub. They change between Orca releases, and this file deliberately no longer lists them. Confirm the app is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and prefer `--json` for agent-driven calls. ## If an older Orca does not recognize `skills get` Use this fallback only when the selected binary explicitly reports that `skills get` is an unknown command. Another failure is not proof of an older binary; report it rather than guessing or changing executables. For a confirmed pre-guide binary, use only this bounded, read-only bootstrap to orient. Do not dead-end and do not invent commands: ```text ORCA status --json ORCA worktree ps --json ORCA terminal list --json ``` Then tell the user that updating Orca restores the full, version-matched guide via `ORCA skills get orca-cli`. Beyond these commands, ask the user rather than guessing a command surface this older binary may not support.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · HK-hub/AgentSkills | 100 | MIT |
| stablyai/orca | 100 | MIT |
Identical content appears in 68 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version fc318aed789b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100orca
Orca is an open-source desktop app that runs several coding agents (Claude Code, Codex, OpenCode and any other terminal agent) side by side, each in its own git worktree, with one CLI to script it. Use when the user wants to race agents on the same task, hand work to another… - 100manta-cli
Operate Manta-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Manta's embedded browser through the `manta` CLI. Use when the user says "$manta-cli", "Manta worktree", "child worktree", "spawn codex/claude in a… - 100helix-cli
Operate Helix-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Helix's embedded browser through the `helix` CLI. Use when the user says "$helix-cli", "Helix worktree", "child worktree", "spawn codex/claude in a… - 90orca-mcp
Drive coding agents running in Orca (stablyai/orca) through the orca-mcp tools: start workers in their own worktrees, watch their state, wait for them to finish, answer them and clean up. Use when the user wants work handed to Claude Code, Codex or another agent inside Orca,… - 100orca-cli-local
Applies local lessons to every use of the Orca CLI (orca-ide, orca-dev). Use alongside the upstream orca-cli skill whenever the Orca CLI is needed, including before creating a branch worktree or asking the user for feedback on a change before committing while running inside Orca. - 100orca-multi
用 Orca 调度 Codex 等执行 agent 自动完成开发任务。用户说“orca-multi <任务>”、要求把任务派给子 agent / 多 agent 并行 / 用 Orca 执行时使用。本会话作为调度端:拆任务、写合同、自动启动执行、校验、打回或验收,最后经用户确认合并。