Orca per-workspace environments: recipe setup and doctor
Resolve the right Orca executable and load the version-matched guide for per-workspace environment recipes
- What
- Resolve the right Orca executable and load the version-matched guide for per-workspace environment recipes
- Cost
- Free
- Needs
- Orca installed (the skill is a discovery stub that loads the version-matched guide from the Orca executable); nothing else — no accounts or keys needed
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @stablyai's Orca environment-recipe helper: resolve the correct Orca executable once per session (ORCA_CLI_COMMAND if set, `orca-dev` in a dev checkout, `orca-ide` on Linux outside Orca-managed terminals — never bare `orca`, which normally resolves to the GNOME Orca screen reader and starts speech on the user's machine), then load the version-matched guide with `ORCA skills get orca-per-workspace-env` before running any command, so per-workspace environment recipes — the on-demand, disposable runtimes (cloud sandbox, VM, SSH host, or local container) Orca creates fresh for each workspace — are stood up end to end, fixed in `environmentRecipes` entries in `orca.yaml`, scaffolded with provider lifecycle scripts, or debugged via `orca vm recipe doctor`. Includes handling for `runtime_access_denied` sandbox errors (re-run with escalated permissions, do not restart Orca) and unknown `skills get` (update Orca; use --help for read-only discovery, never guess unsupported commands). Honest caveats: this is a discovery stub — the real guidance ships inside the installed Orca executable, and it does not work without Orca installed; listed here with credit to its creator; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: Orca installed (the skill is a discovery stub that loads the version-matched guide from the Orca executable); nothing else — no accounts or keys needed Install "Orca per-workspace environments: recipe setup and doctor" for me. A discovery stub for Orca per-workspace environment recipes (on-demand disposable runtimes: cloud sandbox, VM, SSH host, or local container, created fresh per workspace): resolve the correct Orca executable for the session (ORCA_CLI_COMMAND, orca-dev, orca-ide — never bare orca on Linux, which resolves to the GNOME screen reader), then load the version-matched guide with ORCA skills get orca-per-workspace-env before running any command; use it to stand up a recipe end to end, fix environmentRecipes entries in orca.yaml, scaffold provider lifecycle scripts, or resolve orca vm recipe doctor failures. Repository: https://github.com/stablyai/orca/blob/main/skills/orca-per-workspace-env/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, allowed hosts declared in the SKILL.md. 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 "orca-per-workspace-env". 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. install or update Orca so the version-matched guide is available). 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.