Isolated Cloud Sandbox Execution & Untrusted Code Runner Skill

Execute LLM-generated Python, Node.js, and shell scripts safely inside ephemeral microVM sandboxes with strict network egress controls, filesystem quotas,

---
name: sandbox-code-execution
description: Execute LLM-generated Python, Node.js, and shell scripts safely inside ephemeral microVM sandboxes with strict network egress controls, filesystem quotas, and timeout enforcement. Use when working with E2B Sandbox, Cloudflare Sandbox, MicroVM Isolation, Code Interpreter.
triggers:
  - sandbox code execution
  - e2b sandbox
  - cloudflare sandbox
---

# Isolated Cloud Sandbox Execution & Untrusted Code Runner Skill

## 1. When to Use This Skill
Load `skill-sandbox-code-execution` whenever an engineering or operations task involves **E2B Sandbox, Cloudflare Sandbox, MicroVM Isolation, Code Interpreter**. Specifically:
- Execute LLM-generated Python, Node.js, and shell scripts safely inside ephemeral microVM sandboxes with strict network egress controls, filesystem quotas, and timeout enforcement.
- Designing, reviewing, or debugging production configurations without guesswork or deprecated flags.
- Running deterministic pre-flight and post-execution verification checks before reporting completion.

## 2. Prerequisites & Required Environment
- **Target Stack:** E2B Sandbox, Cloudflare Sandbox, MicroVM Isolation, Code Interpreter
- **Permissions:** Read-only inspection by default; ask for explicit confirmation before executing destructive mutations or production deployments.
- **Reference Repository:** `https://e2b.dev/docs`

## 3. Step-by-Step Execution Playbook
1. **Context & Configuration Discovery:**
   Inspect existing project manifests (`package.json`, `wrangler.jsonc`, schema files, or environment declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.
2. **Deterministic Implementation:**
   Apply the canonical patterns for **E2B Sandbox**:
   - Enforce strict schema/type validation at every external boundary.
   - Include explicit error handling, structured logging, and idempotency keys on all mutating calls.
   - Keep secrets in environment variables or secret stores—never hardcode tokens in source files.
3. **Verification & Regression Gate:**
   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.

## 4. Reference Commands & CLI Workflow
```bash
npm i @e2b/code-interpreter
```

## 5. Edge Cases & Anti-Hallucination Guardrails
- **Zero Unverified Claims:** Never claim a deployment, migration, or API call succeeded without inspecting the command output or HTTP status code.
- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.

Synthesized Engineering Blueprint & Setup Guide