orca-cli
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca-np` CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
How do I install this agent skill?
npx skills add https://github.com/nplez1/orca --skill orca-cliIs this agent skill safe to install?
- Gen Agent Trust Hubfail
The skill instructs the agent to use the orca CLI and includes directions to bypass sandbox restrictions by escalating permissions if a command is blocked. It also dynamically loads instructions from the CLI tool at runtime, which could be used to influence agent behavior via indirect prompt injection.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Orca CLI
This discovery stub loads the version-matched guide from the Orca executable used for this session.
Resolve the CLI for this session
This skill drives Orca NP, whose own CLI installs as orca-np. Choose the executable once and
reuse it for every later command:
- If the
ORCA_CLI_COMMANDenvironment variable is set, use its value. Orca NP exports this for the sessions it manages, normally as an absolute path to its own launcher. Substitute it directly, quoted — these paths contain spaces (/Applications/Orca NP.app/…,…/Application Support/…) — with double quotes in POSIX shells,& "…"in PowerShell, and"…"in cmd.exe. - Otherwise, in a dev checkout whose session exposes
ORCA_DEV_REPO_ROOT, useorca-np-dev, the dev launcher the running build installed. Inside the repo,pnpm exec orca-devreaches the same CLI. - Otherwise, use
orca-np.
One case needs a different executable, and it has to be established rather than guessed from what
happens to be on PATH: an Orca host that deployed its own CLI shim to this machine — an
Orca-managed remote or SSH session — names that shim plain orca, so use orca there. Nothing you
merely find on PATH establishes it: outside this app's managed sessions a bare orca is the
official Orca install, which targets a different app and data directory, and on Linux it is normally
the GNOME Orca screen reader (/usr/bin/orca), which starts speech on the user's machine. orca-ide
is the official Linux install too.
Below, ORCA is a placeholder for the executable you resolved. Substitute it before
running anything — quoted as above when it is a path — and do not create a shell variable or run
ORCA literally. The quoting rule above is the only thing that differs between POSIX shells,
PowerShell, and cmd.exe (and a path is safer run directly than through cmd /c, which strips the
outer pair of quotes).
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 version-matched guide before running Orca commands
ORCA skills get orca-cli
Prefer --json. Use the selected executable's --help for commands or flags the guide does
not cover. If a command reports that Orca is not running, start it with ORCA open --json
and retry. If it fails with runtime_access_denied, your sandbox blocked the connection:
re-run it with escalated permissions, and do not run ORCA open or restart Orca. If
skills get is unknown, explain that updating Orca restores the guide; use --help for
read-only discovery and do not guess unsupported commands.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/nplez1/orca/orca-cli">View orca-cli on skillZs</a>