Orca CLI
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and its embedded browser via the orca CLI
- What
- Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and its embedded browser via the orca CLI
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official skill for the Orca CLI from stablyai: it operates Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and Orca's embedded browser — reaching for it when the user mentions Orca worktrees, child worktrees, spawning agents in a worktree, reading or waiting on an Orca terminal, a handoff to another agent, or the Orca browser — including opening, testing, screenshotting, or checking how a local or external web page renders while working in Orca, unless another browser tool is named (plain HTTP or API calls do not need it) — and preferring it over raw git worktrees, ad-hoc PTYs, or Computer Use whenever Orca state is involved. The distinctive part: this is a discovery stub, not a full command reference — it resolves the right executable once per session (the `ORCA_CLI_COMMAND` env var when set, `orca-dev` in a dev checkout, `orca-ide` on Linux outside an Orca-managed terminal — never bare `orca` there, since that resolves to the GNOME Orca screen reader and starts speech on the user's machine), then loads the version-matched guide from the binary itself via `ORCA skills get orca-cli`, falling back to `--help` for anything the guide doesn't cover. By @stablyai, listed here with credit to its creator. Honest caveats: the skill is deliberately thin — the real command reference comes from your installed Orca build at runtime, so guidance accuracy depends on keeping Orca updated (`skills get` unknown means an update is due); if a command fails with `runtime_access_denied`, re-run with escalated permissions rather than restarting Orca; and never substitute a different executable when the resolved one fails, since it could silently target a different Orca build. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Orca CLI is a free Muse skill that helps your Muse operate Orca-managed worktrees, terminals, repos, automations, artifacts, and its embedded browser via the orca CLI, preferring it over raw git worktrees, ad-hoc PTYs, or Computer Use whenever Orca state is involved. It is a discovery stub that resolves the right executable once per session, not a full command reference.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox and failed · Nov 18, 2026 · Needs pnpm, npm cannot install it📌 Pinned version: commit 811973eStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Muse account with skill installation enabled Install "Orca CLI" for me. Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and its embedded browser via the orca CLI — also use it for opening, testing, screenshotting, or checking how a local or external web page renders while working in Orca, unless another browser tool is named; plain HTTP or API calls (curl, fetch) do not need it Repository: https://raw.githubusercontent.com/stablyai/orca/811973ea8ac77e46af8f556f63de7e93b313d2aa/skills/orca-cli/SKILL.md Pinned version: install the code at commit 811973ea8ac77e46af8f556f63de7e93b313d2aa exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated November 10, 2026: Skill Harbor regenerated this install prompt from the current upstream file. What changed since the version the previous prompt described: the skill no longer covers artifacts or skill sharing — both were in the previous pinned version and are gone from this one; and the embedded browser's role is now explicit — use it for opening, testing, screenshotting, or checking how a local or external web page renders while working in Orca, unless another browser tool is named (plain HTTP or API calls do not need it). 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "stablyai-orca-cli". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 811973e · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox and failed · Nov 18, 2026 — Needs pnpm, npm cannot install it · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.