orca-cli

Orchestrate Orca worktrees, terminals, and browser automation via CLI.

40.6k|2.9k|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/stablyai/orca --skill orca-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orca-cli
Source: https://github.com/stablyai/orca/tree/main/skills/orca-cli
Command: npx skills add https://github.com/stablyai/orca --skill orca-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the orchestration of Orca worktrees, terminals, and the built-in browser from a running Orca editor, reducing manual switching and context loss when coordinating multi-part tasks.

Core Features & Use Cases

  • Orchestrate worktrees, inspect and update worktree state, and remove worktrees as part of lifecycle management.
  • Manage live Orca terminals: read, send, wait, or stop outputs, and route results into automated workflows.
  • Drive browser automation inside Orca to navigate, snapshot, click, fill, and capture screenshots for end-to-end testing or QA.

Quick Start

Invoke the public orca CLI to manage worktrees, terminals, and browser automation inside a running Orca editor.

Frequently Asked Questions about orca-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate terminal and worktree management in my code editor?

Run browser automation to navigate, snapshot, click, fill, and capture screenshots for end-to-end testing inside a running Orca editor. The CLI drives the built-in browser to execute QA tasks and outputs JSON for machine processing.

How does worktree lifecycle management work with terminal orchestration?

Worktree lifecycle management works by applying CLI commands to create, inspect, update, or remove worktrees while simultaneously reading, sending to, waiting on, or stopping Orca-managed terminals. This coordinates multi-part tasks without manual context switching.

Do I need a running Orca editor to use the worktree and terminal automation CLI?

Yes, a running Orca editor is required because the CLI relies on the Orca runtime and public Orca surface to execute worktree, terminal, and browser automation commands. It outputs JSON for machine processing within that environment.

Can I capture screenshots and fill forms using built-in browser automation?

Yes, you can capture screenshots and fill forms by driving the built-in browser automation inside Orca to navigate, snapshot, click, and fill elements. This supports end-to-end testing and QA workflows directly from the CLI.

What is the best way to coordinate multi-part tasks across terminals and worktrees?

The best way to coordinate multi-part tasks is using a CLI that orchestrates worktrees and live terminals from a running editor, routing outputs into automated workflows. This reduces manual switching and context loss when managing complex operations.