sandbox-next
An agent skill by cloudflare, from cloudflare/skills. Tags: cloudflare, debugging, development, sandbox, setup.
What it does
Build or maintain Cloudflare Sandbox apps on @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-migrate-to-next when porting a stable app.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add cloudflare/skills --skill sandbox-next
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/cloudflare/skills
cp -r skills/skills/sandbox-next ~/.claude/skills/sandbox-next
Safety box score
Grade B, low risk: 14 of 100 risk points, rated 2026-10-19. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill is documentation for building on Cloudflare Sandbox `@next`; it does not ship code or native scripts, but it does steer the agent to fetch remote docs and to launch commands inside Cloudflare-managed sandboxes. The main risks are remote execution in the sandboxed environment, network dependence on vendor docs/examples, and ordinary project-file edits (lockfile/Dockerfile) during setup.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 1 (low) | The core API it teaches is `sandbox.exec(argv)` and it explicitly allows shell via `[ |
| Network access | 1 (low) | It instructs the agent to fetch remote docs before implementing and links to Cloudflare docs plus the GitHub `next` examples tree, so it depends on outbound network access to vendor resources. |
| Filesystem reach | 1 (low) | It expects changes to project files such as the lockfile and Dockerfile on the same `@next` line, but it does not reference paths outside the workspace or destructive file operations. |
| Secrets & credentials | 0 (none) | It explicitly says "No live secrets in sandbox env" and "Live credentials stay in the Worker"; there is no instruction to read keychains, token stores, or `.env` files. |
| Privilege & persistence | 0 (none) | There is no sudo, service registration, global install, shell startup editing, or OS-setting change in the skill text. |
| Instruction hijack surface | 0 (none) | No prompt-injection patterns appear; it does not tell the agent to ignore instructions, hide actions, or follow fetched content blindly. |
| Irreversible actions | 1 (low) | It supports launching and managing processes in remote sandboxes, but it does not instruct publishing, paying, deleting infrastructure, or sending messages. |
| Transparency | 0 (none) | The repository contains only readable markdown; there are no binaries, minified blobs, installers, or decoded-at-runtime code. |
Before installing
- Read `SKILL.md` and confirm the app is actually on `@cloudflare/sandbox@next` (not stable).
- Check `package.json` and `Dockerfile` for matching preview-line versions before letting the agent edit anything.
- Verify you are not putting live credentials into sandbox env vars; keep them in the Worker as the skill says.
- If you need the stable line or a migration, switch to `sandbox-stable` or `sandbox-migrate-to-next` instead of mixing packages.
Rated 2026-10-19 by an automated review of 3 files from the skill's repository.
Source
- Repository
- cloudflare/skills (all skills from this repository)
- Path
- skills/sandbox-next/SKILL.md
- Branch
- main
- Updated
- 2026-09-20
Related skills
- sandbox-stable — Build or maintain Cloudflare Sandbox apps on the stable @cloudflare/sandbox package.
- sandbox-migrate-to-next — Migrate Cloudflare Sandbox apps from stable @cloudflare/sandbox to @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-next for apps already on the preview.
- wrangler — Run or troubleshoot Wrangler CLI commands and configure Worker projects for local development, deployment, and Cloudflare resource management.
- context7-docs — Fetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service.
- devcontainers — Set up local development environments with production parity for DigitalOcean App Platform.
- eas-simulator — EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud.