Orca skills registry & MCP
Install Orca agent skills with npx skills add. Hybrid stubs stay thin; orca skills get serves the version-matched guide. Orca updates its own skills without npx.
Orca ships skills that agents install into their skill directories. Public install packages are hybrid discovery stubs: short SKILL.md files that tell the agent when to engage Orca and how to load the full guide from the running CLI. Command flags live in the binary so they cannot drift from the app version.
Installable Orca skills
Use npx skills add with the public Orca repo and the skill name. Default agent setup usually installs orca-cli, orca-computer-use, and orchestration.
| Skill | Install | Use it for |
|---|---|---|
orca-cli | npx skills add https://github.com/stablyai/orca --skill orca-cli --global | Worktrees, terminals, files, automations, embedded browser. |
orchestration | npx skills add https://github.com/stablyai/orca --skill orchestration --global | Multi-agent Runs, tasks, supervised workers, messages, gates. |
orca-computer-use | npx skills add https://github.com/stablyai/orca --skill orca-computer-use --global | Desktop apps via accessibility trees and safe UI actions. |
orca-linear | npx skills add https://github.com/stablyai/orca --skill orca-linear --global | Linear ticket read/write through orca linear. |
orca-emulator | npx skills add https://github.com/stablyai/orca --skill orca-emulator --global | iOS Simulator control. |
orca-emulator-android | npx skills add https://github.com/stablyai/orca --skill orca-emulator-android --global | Android emulator/device via adb. |
orca-per-workspace-env | npx skills add https://github.com/stablyai/orca --skill orca-per-workspace-env --global | Per-workspace environment recipes (orca.yaml). |
orca-plugin-authoring | npx skills add https://github.com/stablyai/orca --skill orca-plugin-authoring --global | Build, debug and publish Orca plugins. |
Hybrid stubs vs the live guide
After npx skills add, agents see a short stub that says:
- Resolve the CLI executable for this session (
ORCA_CLI_COMMAND,orca-dev, Linuxorca-ide, elseorca). - Load the full guide:
orca skills get <topic>(or--fullfor the long guide). - Prefer
--jsonand do not invent flags from memory.
orca skills list
orca skills get orca-cli
orca skills get orchestration --references
orca skills get orchestration --reference recovery-and-cleanup
orca skills get orchestration --full
orca skills get orca-linear --json
A guide's action gates name conditional references. --reference <name> prints one of them alone, so an agent pays for the kernel plus that document instead of the whole package; --references lists the names. The name may be bare (recovery-and-cleanup) or spelled as the guide writes it (references/recovery-and-cleanup.md). --full still prints the kernel plus every reference.
Add --json when an agent needs deterministic output for automation. skills show is an alias for skills get.
Keep skills up to date
Orca updates its own skills itself, with no npx, Git, Node or network. A copy counts as Orca's untouched copy when its folder holds only SKILL.md and that file matches a version Orca has shipped. Only those copies are rewritten, in place (the shared ~/.agents/skills/<name> or a real folder in an agent's skills folder such as ~/.claude/skills/<name>). Anything else is left alone and reported: You've changed this copy, or A different skill already uses this name. Orca never deletes a folder it did not create.
When this Orca build ships a newer version of a skill you installed, the app:
- Shows an update available nudge and badge. Update only touches locations that already hold the skill; it never adds the skill for another agent.
- Opens Update skills, which lists every location and what Update does there: No change, Will update, Will link, or Left alone with the reason. A copy left alone has a Replace choice (off by default); Replace first moves that copy to
~/.agents/.orca-skill-backups/, then puts Orca's copy in its place. - Runs exactly the plan you reviewed: if a folder changed after you opened the dialog, that skill reports Changed since you reviewed it and nothing is written there.
- Shows the result per skill, for example
Updated · 1 left alone: You've changed this copy, and a status-bar segment while it runs.
This covers skills installed on this computer. The app does not check WSL projects, SSH hosts or paired Orca servers yet; run orca skills update there.
On headless hosts (SSH, containers, CI, orca serve) use the CLI. It runs the same planner on the machine that runs it and does not need a running Orca app:
orca skills install # list installable names
orca skills install --skill orca-cli --skill orchestration
orca skills install --skill orca-cli --agent claude,codex
orca skills update --all --dry-run # what would change, and the plan digest
orca skills update --all
orca skills update --all --force # also replace copies left alone (backup kept)
- Default scope is global; pass
--localfor the current project only (Orca links only into agent folders the project already has). - Targets the agents Orca detects on the host plus the shared
.agents/skillsfolder. Use--agent <name>[,<name>…]to choose (the skills CLI's keys such asclaude-codestill work), or--agent universalfor the shared folder alone. updateonly touches locations that already hold the skill;installadds it, including for newly detected agents.--dry-runprints the plan and its digest without writing. A real run plans again and writes only while the plan still matches.--jsonworks for dry runs and real runs. The exit code is 1 when a location failed or changed during the run; folders left alone are warnings.
Install and delete from the Skills page
When an in-app install asks for a workspace target, search the picker by workspace name or by kind (worktree / folder). The agent picker separates directories Orca always includes from additional agent directories you can select, so you can review the exact installation targets before continuing.
To remove a scanned skill, open its actions menu and choose Delete…. For several skills, open the page's More actions menu, choose Delete skills…, and select the eligible results. Orca explains why a copy cannot be deleted—for example because it is bundled, plugin-managed, read-only, or outside a removable skill folder—before you confirm. This is separate from Manage installs, which manages copies installed from shared links.
Share private skills between hosts
Open Skills → Share skills to publish one skill or a bundle behind one unlisted, revocable link. Publishing requires your Orca account. Review the included files, scripts, executables, digest, and optional release notes before you publish; each published version is immutable, so later local edits do not silently change what recipients install.
Anyone with an active link can inspect and install the shared skills without signing in, so treat the link like a credential. A recipient reviews the exact version, chooses all or a subset of its skills, then selects global or workspace scope on this computer, a paired Orca runtime, WSL, or an SSH host. Existing modified skills default to Keep local. Use Skills → Manage installs to update, roll back, or remove copies Orca installed, and Settings → Share Skills to copy or revoke your active links. Revoking a link blocks future access but does not remove copies already installed.
Agents can publish an explicitly named set from the CLI after you enable the separate, default-off Settings → Share Skills → Allow agents and the Orca CLI to publish skill links permission:
orca skills installed --json
orca skills share --skill frontend --skill testing --bundle-name "Team Toolkit" --json
skills installed returns safe selectors without exposing local paths. skills share accepts exact discovery IDs or unambiguous names; it does not accept arbitrary paths or --all.
orca-cli
npx skills add https://github.com/stablyai/orca --skill orca-cli --global
After install, load the version-matched command guide with orca skills get orca-cli. See Orca CLI.
orchestration
npx skills add https://github.com/stablyai/orca --skill orchestration --global
Use this when an agent should coordinate other agents through Runs, tasks, supervised workers, and decision gates. See Orchestration. Always load orca skills get orchestration --full before mutating orchestration state — the legacy orchestration run command is retired.
orca-computer-use
npx skills add https://github.com/stablyai/orca --skill orca-computer-use --global
Use this when an agent needs to inspect and operate local desktop app windows. See Computer use.
orca-linear
npx skills add https://github.com/stablyai/orca --skill orca-linear --global
Agents should load orca skills get orca-linear before mutating tickets. Covers issue --full, save-issue, list-issues, relations, completion attach+comment flow, and untrusted-ticket rules. Existing linear-tickets installs still resolve. See CLI reference → Linear.
orca-emulator
npx skills add https://github.com/stablyai/orca --skill orca-emulator --global
Use this when an agent should control an iOS Simulator from inside Orca through orca emulator commands.
orca-emulator-android
npx skills add https://github.com/stablyai/orca --skill orca-emulator-android --global
Use for adb-connected Android AVDs/devices: list/boot, tap/swipe/type, hardware buttons, install/launch, permissions, accessibility tree, logcat. Load details with orca skills get orca-emulator-android.
orca-per-workspace-env
npx skills add https://github.com/stablyai/orca --skill orca-per-workspace-env --global
Use when setting up or debugging per-workspace environment recipes in orca.yaml. See Ways to run Orca.
orca-plugin-authoring
npx skills add https://github.com/stablyai/orca --skill orca-plugin-authoring --global
Use when an agent should make, debug, test or publish an Orca plugin: themes, syntaxes, custom editors, TSX components panels and worker commands. Load it with orca skills get orca-plugin-authoring; its references (components, host API, events, manifest fields, CLI) are generated from the running Orca.
Discovery sources
Orca's skill UI scans installed skill homes for Claude, Codex, Agent Skills, and OMP (~/.omp/agent/skills), so skills placed there show up without a manual symlink.
Add your own skills
Any repo with a skills/<name>/SKILL.md file can be installed via npx skills add. Point your agent at internal repos to give it company-specific powers.
MCP servers
Model Context Protocol (MCP) servers expose external tools to compatible agents. Register MCP endpoints under Settings → Integrations → MCP; those tools appear inside agent CLIs that support MCP.