orca-per-workspace-env
Configure Orca Workspace Environments
Per-workspace environment recipes can fail because CLI selection and provider lifecycle details vary. This skill loads Orca guidance matched to the active version.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "orca-per-workspace-env" from https://skillstore.io/skills/stablyai-orca-per-workspace-env.md and its manifest at https://skillstore.io/api/skills/stablyai-orca-per-workspace-env/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "orca-per-workspace-env". Determine the Orca executable for a managed WSL session.
Expected outcome:
Use the executable specified by the managed session after validating it. Keep that selection for every later Orca command.
Using "orca-per-workspace-env". Explain why recipe doctor fails during environment startup.
Expected outcome:
- The failure occurs during the provider startup stage.
- Verify the lifecycle script, required inputs, and cleanup behavior against the version-matched guide.
- Report the exact CLI error if the selected executable cannot run.
Security Audit
High RiskAll 17 static alerts are false positives caused by Markdown formatting or prose references to command shells. However, executable selection from an environment variable and runtime loading of unaudited guidance create high-risk trust boundaries.
Confirmed security concerns (2)
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/stablyai-orca-per-workspace-env/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/stablyai-orca-per-workspace-env?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/stablyai-orca-per-workspace-env?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/stablyai-orca-per-workspace-env/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/stablyai-orca-per-workspace-env.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
stablyai. (2026). orca-per-workspace-env security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/stablyai-orca-per-workspace-env/audits/1BibTeX citation
@techreport{stablyai-stablyai-orca-per-workspace-env-2026,
author = {stablyai},
title = {orca-per-workspace-env security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/stablyai-orca-per-workspace-env/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "orca-per-workspace-env security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "stablyai"
date-released: "2026-09-10"
url: "https://skillstore.io/skills/stablyai-orca-per-workspace-env/audits/1"
identifiers:
- type: other
value: "skillstore:stablyai-orca-per-workspace-env:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Create a workspace recipe
Build a disposable environment recipe and verify its provider lifecycle steps.
Repair recipe configuration
Review an environmentRecipes entry and resolve validation or doctor failures.
Select the correct CLI
Determine which Orca executable matches the current local, WSL, or managed session.
Try These Prompts
Identify the correct Orca executable for this session. Explain the evidence and stop if the selected executable fails.
Review my environmentRecipes entry, load the version-matched guide, and identify configuration errors without guessing unsupported fields.
Analyze this Orca recipe doctor failure. Trace it to the recipe or provider lifecycle stage and propose verified corrections.
Design a complete per-workspace environment recipe for my provider. Include lifecycle responsibilities, validation steps, failure handling, and cleanup requirements.
Best Practices
- Resolve the Orca executable once and reuse it throughout the session.
- Prefer structured command output when the installed CLI supports it.
- Stop and report exact errors instead of switching silently to another Orca build.
Avoid
- Do not run bare orca on Linux outside an Orca-managed terminal.
- Do not execute the ORCA placeholder literally or store it as a shell variable.
- Do not guess unsupported commands, flags, or recipe fields.