Back to skills

Agent Skill

Orca Cli

orca-cli

Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca` 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.

StablyaiToolsTypeScriptAdeAgent-ideAi-agentsAutomationBotClaude-codeCodexGhosttyGrok-botHermes-agentMobile-appMuseOpenclawOpencodeOrchestrationPiRuntimeTerminalWorktreesYc-backed
github.com/stablyai/orca/tree/main/skills/orca-cli

333K installs

•

stablyai/orca

•

by Stablyai

Score

9.1

/ 10

Installs

333K

Repo Stars

98.6K

Last Updated

0d ago

Fresh

Quality Ratio

99%

Description

Verified

Language

TypeScript

First Published

Apr 2026

Summary

The Orca Cli agent skill enables programmatic control over Orca-managed worktrees, terminals, repositories, automations, and its embedded browser, treating the Orca IDE as the source of truth for development state. This is essential for developers and agents operating within the Orca integrated development environment who need to manage complex, stateful coding workflows. This agent skill is adopted by a significant user base, marked as a skill with 3K installs in the registry. It enables agents to manage `orca worktree` lifecycles, interact with `orca terminal` sessions using `read` and `send` commands, and control the built-in `orca browser` with a `snapshot-interact-re-snapshot` pattern. This skill explicitly guides agents to prefer `orca` commands, often using `--json` output, for operations touching Orca-managed state, rather than generic `git` or external browser tools. Agents should note the distinction between Orca's embedded browser, controlled by this skill, and external browser windows or desktop UI, which require the Computer Use skill.

Skill Definition

This discovery stub loads the version-matched guide from the Orca executable used for this session.

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 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 to Use

Use in O-mega

Claude Code

npx skills add stablyai/orca orca-cli