orca-per-workspace-env

Set up, debug, and validate Orca per-workspace environment recipes and lifecycle scripts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configuring disposable per-workspace runtimes (cloud sandboxes, VMs, or local environments) in Orca involves provider prerequisites, base and auth snapshots, credentials, and lifecycle scripts that are easy to misconfigure. This Skill guides setup, review, and debugging of environmentRecipes entries in orca.yaml so each workspace gets a fresh, working environment.

Core Features & Use Cases

  • First-time environment setup: Walks through provider prerequisites, the reusable base snapshot, the coding-agent auth snapshot, credentials, and state.
  • Recipe scaffolding and repair: Fixes an environmentRecipes entry in orca.yaml and scaffolds provider lifecycle scripts.
  • Diagnostics: Resolves orca vm recipe doctor failures using the version-matched guide served by the Orca binary via orca skills get orca-per-workspace-env.
  • Use Case: A developer adds a new cloud sandbox provider to their repo, runs the recipe doctor, hits a validation failure, and uses this Skill to identify the misconfigured snapshot and correct the lifecycle scripts.

Quick Start

Ask the assistant to set up or debug an Orca per-workspace environment recipe for your repository and validate it with the recipe doctor.

Frequently Asked Questions about orca-per-workspace-env

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

FAQPage Schema
How do I set up a per-workspace environment in Orca?

Run `orca skills get orca-per-workspace-env` to load the version-matched guide, then follow its steps for provider prerequisites, the base snapshot, the auth snapshot, and credentials. Confirm the app is running with `orca status --json` before executing recipe commands.

How do I fix an environmentRecipes entry in orca.yaml?

Use the recipe doctor: run `orca vm recipe doctor <recipe-id> --repo-path <repo> --json` to get a free static check of the entry. The Skill's guide explains each reported failure and how to correct the configuration or lifecycle scripts.

Why does the orca command launch a screen reader on Linux?

Outside Orca-managed terminals on Linux, bare `orca` resolves to the GNOME Orca screen reader at /usr/bin/orca. Use `orca-ide` instead, or `orca-dev` in a dev checkout with ORCA_DEV_REPO_ROOT set.

What if my Orca version does not recognize the skills get command?

Use the bounded read-only fallback: `orca status --json` and `orca vm recipe doctor <recipe-id> --repo-path <repo> --json`. Then update Orca to restore the full version-matched guide, and never add `--provision` without explicit user approval.

Can the recipe doctor create cloud resources automatically?

No. The default doctor run is a free static check. The `--provision` flag creates provider resources and may incur costs, so it must never be used without the user's explicit approval.