Cloudflare Browser Rendering
cloudflare/moltworker
Drives headless Chrome through Cloudflare Browser Rendering over a CDP WebSocket to take screenshots, navigate and scrape pages, and record multi-page videos.
Migrate Cloudflare Sandbox apps from stable @cloudflare/sandbox to @cloudflare/sandbox@next (SDK 1.0 preview).
OfficialApache-2.0Auto-check passed
Install Sandbox Migrate To Next
$ npx skills add cloudflare/skills --skill sandbox-migrate-to-next -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cloudflare/skills sandbox-migrate-to-next --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cloudflare/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sandbox-migrate-to-next .claude/skills/sandbox-migrate-to-next && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sandbox-migrate-to-next" agent skill from https://github.com/cloudflare/skills/tree/main/skills/sandbox-migrate-to-next into .claude/skills/sandbox-migrate-to-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-migrate-to-next", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cloudflare/skills/tree/main/skills/sandbox-migrate-to-nextType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cloudflare/skills --skill sandbox-migrate-to-next -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cloudflare/skills sandbox-migrate-to-next --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cloudflare/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sandbox-migrate-to-next .agents/skills/sandbox-migrate-to-next && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sandbox-migrate-to-next" agent skill from https://github.com/cloudflare/skills/tree/main/skills/sandbox-migrate-to-next into .agents/skills/sandbox-migrate-to-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-migrate-to-next", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cloudflare/skills --skill sandbox-migrate-to-next -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cloudflare/skills sandbox-migrate-to-next --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cloudflare/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sandbox-migrate-to-next .cursor/skills/sandbox-migrate-to-next && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sandbox-migrate-to-next" agent skill from https://github.com/cloudflare/skills/tree/main/skills/sandbox-migrate-to-next into .cursor/skills/sandbox-migrate-to-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-migrate-to-next", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cloudflare/skills.git --path skills/sandbox-migrate-to-next--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cloudflare/skills --skill sandbox-migrate-to-next -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cloudflare/skills sandbox-migrate-to-next --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cloudflare/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sandbox-migrate-to-next .gemini/skills/sandbox-migrate-to-next && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sandbox-migrate-to-next" agent skill from https://github.com/cloudflare/skills/tree/main/skills/sandbox-migrate-to-next into .gemini/skills/sandbox-migrate-to-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-migrate-to-next", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cloudflare/skills sandbox-migrate-to-nextInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cloudflare/skills --skill sandbox-migrate-to-next -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cloudflare/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sandbox-migrate-to-next .github/skills/sandbox-migrate-to-next && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sandbox-migrate-to-next" agent skill from https://github.com/cloudflare/skills/tree/main/skills/sandbox-migrate-to-next into .github/skills/sandbox-migrate-to-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-migrate-to-next", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cloudflare/skills --skill sandbox-migrate-to-next -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cloudflare/skills sandbox-migrate-to-next --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cloudflare/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sandbox-migrate-to-next .opencode/skills/sandbox-migrate-to-next && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sandbox-migrate-to-next" agent skill from https://github.com/cloudflare/skills/tree/main/skills/sandbox-migrate-to-next into .opencode/skills/sandbox-migrate-to-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-migrate-to-next", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sandbox-migrate-to-next- GitHub stars
- 3k
- Used in
- 3 other repos
- Token cost
- ~2k tokens
- SKILL.md length
- 622 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Migrate Cloudflare Sandbox apps from stable @cloudflare/sandbox to @cloudflare/sandbox@next (SDK 1.0 preview).
- Works in 5 steps: Review hard rules and the replacement map → Audit the codebase; list hits and target… → Clarify with the user (cutover, bridge,… → …
- SKILL.md covers Workflow, Hard rules, Replacement map and Audit, plus 4 more sections
- Calls rg, npm and npx
What it does
Sandbox Migrate To Next is an agent skill from cloudflare/skills, published by the product's own GitHub organization. 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.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Cloudflare. The repository describes itself as: Skills for teaching agents how to build on Cloudflare. The licence is Apache-2.0.
Example prompts
- “/sandbox-migrate-to-next”
Requirements
- Python 3
- Node.js
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Review hard rules and the replacement map
- Audit the codebase; list hits and target shapes
- Clarify with the user (cutover, bridge, Python image, unclear sites)
- Upgrade package, image, and code
- Validate
What it can do on your machine
Read from SKILL.md and the folder at commit a18ffe2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
rgnpmnpx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developers.cloudflare.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sandbox Migrate To Next loads about 2k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 622 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cloudflare/skills at commit a18ffe2, republished under its Apache-2.0 licence (© cloudflare). 622 words, ~1,967 tokens.
Download SKILL.mdSave it as
.claude/skills/sandbox-migrate-to-next/SKILL.md (or your agent's skills folder).- name
- sandbox-migrate-to-next
- description
- 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.
Migrate stable → Sandbox SDK 1.0 preview (@next)
Perform the port. Follow the steps in order. Depth lives in docs—fetch the linked page when a step needs detail.
Human guide: Migrate · 1.0 preview
New projects should start on @next (sandbox-next), not this skill. Day-to-day stable work → sandbox-stable. Deprecated-API cleanup without moving to @next → 2026 deprecation guide first if needed.
Existing apps should migrate when you can, so you are ready when 1.0 becomes the stable release. Do not force production cutover without the user agreeing.
Prefer installed @next types and the migrate doc over memory.
Workflow
- Review hard rules and the replacement map
- Audit the codebase; list hits and target shapes
- Clarify with the user (cutover, bridge, Python image, unclear sites)
- Upgrade package, image, and code
- Validate
Stop after any step that needs a user decision.
Hard rules
- Worker package and container image must be the same
@nextline. - Production cutover uses immediate container rollout. Stable and
@nextcontrol protocols are incompatible both ways; gradual rollout leaves a broken mixed window. In-flight container work can stop. - After cutover,
await sandbox.exec(...)means process started, not command finished. - Argv is as-is (no implicit shell). Shell syntax needs an explicit shell binary.
- Process handles have no stdin → terminals for interactive input.
- Observation
timeout/AbortSignalcancel the wait only, not the process. - No single retry loop for every error.
- Do not invent APIs (
gitCheckouton core, process stdin, string-exec completion helper). - Self-deployed bridge stays on stable (not part of the preview line yet).
Replacement map
| Stable | @next |
|---|---|
SANDBOX_TRANSPORT / transport / setTransport | Remove — RPC only |
await sandbox.exec("cmd") → buffered result | await sandbox.exec(argv) → handle, then output / waits |
execStream / startProcess | Same handle: logs, waitFor*, kill |
| Default / named sessions | Gone — cwd/env per launch, or one shell script |
sandbox.terminal(request) / session terminal | createTerminal + terminal.connect(request) |
xterm sessionId | terminalId |
Interpreter methods on Sandbox | withInterpreter → sandbox.interpreter.* |
gitCheckout | argv git via exec |
| String kill signals | Numeric only |
Files, mounts, backups, ports, tunnels, proxyToSandbox | Mostly unchanged (ignore session/transport bits on stable pages) |
Depth: Migrate · after port, day-to-day → sandbox-next
Audit
rg 'SANDBOX_TRANSPORT|transport:|setTransport|enableDefaultSession|createSession|getSession|deleteSession|execStream\(|startProcess\(|killProcess\(|sandbox\.terminal\(|sessionId|gitCheckout\(|SandboxTransport|ExecutionSession'Also: string exec(, cd then a later exec, bare createCodeContext / runCode on Sandbox.
Clarify (ask when needed)
- OK to cut production with
--containers-rollout=immediate(live processes/terminals/streams may stop)? - Self-deployed bridge? Leave on stable.
- Python interpreter →
-pythonimage variant? - Call sites not covered by the map?
Show full SKILL.md (242 more words)Show less
Upgrade
Package and image
npm install @cloudflare/sandbox@nextFROM cloudflare/sandbox:next
# Python: cloudflare/sandbox:next-pythonSame prerelease tag on Worker and image when not on floating next.
Code by area
Apply replacements from the map. For each area, implement from the doc—not from stable habits:
| Area | Doc |
|---|---|
| Commands / handles / waits | Processes · Processes API |
cwd / env / secrets | Environment · Outbound traffic |
| Drop sessions | Migrate · Lifecycle |
| Terminals | Terminals |
| Interpreter | Interpreter |
| Errors | Errors |
| Durable job across requests | Process execution — lifetime / durability |
Commands (shape):
// Before (stable)
const result = await sandbox.exec("npm test");
// After (@next)
const process = await sandbox.exec(["/bin/bash", "-lc", "npm test"]);
const result = await process.output({ encoding: "utf8" });const server = await sandbox.exec(["/bin/bash", "-lc", "npm run dev"], {
cwd: "/workspace/app",
});
await server.waitForPort(3000, { timeout: 60_000 });
await server.kill(); // numeric; default 15Terminals (shape):
const terminal = await sandbox.createTerminal({ command: ["bash"], cwd: "/workspace" });
const t = await sandbox.getTerminal(terminal.id);
if (!t) return new Response("terminal gone", { status: 410 });
return t.connect(request, { cursor, cols, rows });Interpreter (shape):
import { Sandbox as BaseSandbox } from "@cloudflare/sandbox";
import { withInterpreter } from "@cloudflare/sandbox/interpreter";
export class Sandbox extends BaseSandbox<Env> {
interpreter = withInterpreter(this);
}Git (shape):
const clone = await sandbox.exec(
["git", "clone", "--depth", "1", "--", repoUrl, "/workspace/repo"],
{ cwd: "/workspace" },
);
const result = await clone.output({ encoding: "utf8" });Delete transport settings entirely. Remove session APIs. Isolate users with separate sandbox IDs.
Deploy cutover
Staging/branch first. Production is one deploy of matching Worker + image:
npx wrangler deploy --containers-rollout=immediateLeave rollout_active_grace_period at default 0 (or set 0 if raised). After cutover, pre-deploy process/terminal IDs are invalid. Details: Migrate · Container rollouts
Validate
- Lockfile + Dockerfile on the same
@nextline - Typecheck against
@next - Smoke argv
exec+output({ encoding: "utf8" }) - Smoke long process / terminal / interpreter if used
- Errors distinguished: unavailable / interrupted-RPC / stale / local wait
- No live secrets in sandbox env
- Grep again for removed APIs
- Production used
--containers-rollout=immediate
Then day-to-day work uses sandbox-next.
Red flags — stop and fix
- Mixing
@nextWorker with stable image (or reverse) - Gradual container rollout for this cutover
- Treating
await execas command completion - Assuming
cd/ exports persist acrossexeccalls - One retry wrapper for every error
- Inventing
gitCheckout, process stdin, or undocumented APIs - Keeping pre-cutover process/terminal IDs after deploy
- Forcing production cutover without user agreement
- Putting live secrets in
setEnvVars/ launchenv
© cloudflare, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/sandbox-migrate-to-next of cloudflare/skills.
Open the folder on GitHubat commit a18ffe2
Used in 3 other repositories
We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in cloudflare/skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Sandbox Migrate To Next next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sandbox Migrate To Next this skillcloudflare/skills | 3k | 3 repos | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Cloudflare Browser Renderingcloudflare/moltworker | 10k | — | ~742 | Automated safety check: Pass | Apache-2.0 | |
| Star Office UI Setupringhyacinth/Star-Office-UI | 7.5k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Cloudflarehodgef/apiker | 127 | 7 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Webhome Extension Builderwebhtv/webhtv | 1.7k | — | ~2.8k | Automated safety check: Pass | GPL-3.0 | |
| Golivemikehasa/golive-skill | 1.2k | — | ~13k | Automated safety check: Notes | MIT |
Similar skills
- Official
Star Office UI Setup
ringhyacinth/Star-Office-UI
Sets up Star Office UI, a pixel-art office dashboard that shows AI agent states, lets other agents join and can be opened from a phone or a public link.
Cloudflare
hodgef/apiker
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF…
Webhome Extension Builder
webhtv/webhtv
Build, review, debug, reverse-engineer, and package WebHome injected extension scripts for FongMi/WebHome App WebView pages.
Golive
mikehasa/golive-skill
Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS).
Webhome Homepage Builder
webhtv/webhtv
Build, review, debug, reverse-engineer data sources for, and package FongMi/WebHome custom homepage single-file HTML.
More from cloudflare/skills
All 16 skills in this repo- Official
Turnstile Spin
cloudflare/skills
Set up, repair, or migrate to Cloudflare Turnstile bot verification in an existing frontend and backend, including server-side Siteverify.
- Official
Nextjs On Cloudflare
cloudflare/skills
Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext.
- Official
Agents SDK
cloudflare/skills
Build, debug, or review Cloudflare Agents SDK applications using the agents package.
- Official
Durable Objects
cloudflare/skills
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
- Official
Sandbox Next
cloudflare/skills
Build or maintain Cloudflare Sandbox apps on @cloudflare/sandbox@next (SDK 1.0 preview).
- Official
Cloudflare One Migrations
cloudflare/skills
Assess and plan migrations from existing VPN, SWG, or SASE platforms to Cloudflare One, including policy mapping, parity gaps, and rollout.
Related
Works with
Questions about Sandbox Migrate To Next
What does Sandbox Migrate To Next do?
Migrate Cloudflare Sandbox apps from stable @cloudflare/sandbox to @cloudflare/sandbox@next (SDK 1.0 preview). Sandbox Migrate To Next is an agent skill from cloudflare/skills, published by the product's own GitHub organization.0 preview).
How do I install Sandbox Migrate To Next in Claude Code?
Run `npx skills add cloudflare/skills --skill sandbox-migrate-to-next -a claude-code`. Or copy the skill folder (skills/sandbox-migrate-to-next in cloudflare/skills) into .claude/skills/sandbox-migrate-to-next in your project. Claude Code loads it when a task matches its description.
How do I install Sandbox Migrate To Next in Codex?
Run `npx skills add cloudflare/skills --skill sandbox-migrate-to-next -a codex`. Or copy the skill folder (skills/sandbox-migrate-to-next in cloudflare/skills) into .agents/skills/sandbox-migrate-to-next in your project. Codex loads it when a task matches its description.
Can I use Sandbox Migrate To Next in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cloudflare/skills --skill sandbox-migrate-to-next -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sandbox-migrate-to-next, .gemini/skills/sandbox-migrate-to-next, .github/skills/sandbox-migrate-to-next and .opencode/skills/sandbox-migrate-to-next in your project.
What does Sandbox Migrate To Next need to run?
Going by SKILL.md and its folder, Sandbox Migrate To Next needs the command-line tools its instructions call (rg, npm and npx). Our summary lists: Python 3; Node.js.
Does Sandbox Migrate To Next access the network?
SKILL.md names 1 domain. As links in the text: developers.cloudflare.com. This is read from the text; nothing was executed.
Is Sandbox Migrate To Next safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sandbox Migrate To Next use?
Sandbox Migrate To Next is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sandbox Migrate To Next use?
About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sandbox Migrate To Next?
Skills that share tags, products or a category with Sandbox Migrate To Next: Cloudflare Browser Rendering (cloudflare/moltworker, 10k stars), Star Office UI Setup (ringhyacinth/Star-Office-UI, 7.5k stars), Cloudflare (hodgef/apiker, 127 stars) and Webhome Extension Builder (webhtv/webhtv, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sandbox Migrate To Next?
cloudflare (a GitHub organization, an official publisher) maintains it in cloudflare/skills, which has 3,016 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 9, 2026.
Source: cloudflare/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.