What problem does it solve?
Cloudflare Sandbox SDK 1.0 preview (@cloudflare/sandbox@next) introduces breaking API changes versus the stable package, and outdated knowledge leads to wrong code. This Skill gates the correct package line, enforces the new process/terminal/interpreter contracts, and routes you to the right preview documentation before writing code.
Core Features & Use Cases
- Package Line Gate: Verifies the npm dependency and container image are both on the @next preview line, and redirects to sandbox-stable or sandbox-migrate-to-next when they are not.
- API Contract Enforcement: Codifies non-negotiable behaviors such as argv-based exec returning a process handle, no implicit shell, no process stdin, per-launch cwd/env, and explicit kill semantics.
- Documentation Retrieval Map: Maps each task (processes, terminals, interpreter, lifecycle, environment, errors, files, mounts, tunnels, preview URLs) to the exact preview docs page, plus a quick-reference cheatsheet and examples index.
- Use Case: You are building a Worker that runs Python code in an isolated sandbox. The Skill confirms you are on @next, gives you the correct exec/output pattern, and points you to the interpreter and lifecycle docs so you avoid removed stable APIs like gitCheckout or string-based exec.
Quick Start
Ask the agent to build a Cloudflare Worker that executes Python code in a sandbox using the @cloudflare/sandbox@next package and returns the output.