Orca CLI
Operate Orca-managed worktrees, terminals, repos, automations, artifacts, and its embedded browser via the orca CLI
- What
- Operate Orca-managed worktrees, terminals, repos, automations, artifacts, 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, artifacts, skill sharing, 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, 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:
Install
Prerequisites: a Muse account with skill installation enabled Install "Orca CLI" for me. Operate Orca-managed worktrees, terminals, repos, automations, artifacts, and its embedded browser via the orca CLI Repository: https://github.com/stablyai/orca/blob/main/skills/orca-cli/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.