Cloudflare Sandbox SDK migration to 1.0 preview
Port Cloudflare Sandbox apps from stable @cloudflare/sandbox to the 1.0 preview — audit, API replacement map, hard rules, validation
- What
- Port Cloudflare Sandbox apps from stable @cloudflare/sandbox to the 1.0 preview — audit, API replacement map, hard rules, validation
- Cost
- Free
- Needs
- an existing app on @cloudflare/sandbox stable that you want to port to the 1.0 preview; npm, wrangler and Docker access; your explicit agreement is required before any production cutover
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — Cloudflare's official migration skill for porting Sandbox apps from stable `@cloudflare/sandbox` to the `@next` 1.0 preview SDK. It runs an ordered workflow: review the hard rules and the stable→preview replacement map (transports removed, argv-as-is `exec` handles, sessions gone in favor of per-launch cwd/env, `createTerminal`, interpreter changes, numeric kill signals), audit the codebase with a ready-made grep for removed APIs, clarify user decisions (cutover, bridge, Python image), upgrade package/image/code with worked shape examples (commands, terminals, interpreter, git), then validate (matching Worker + image line, typecheck, smoke tests, grep again, no live secrets in sandbox env). The red-flags list is the best part: never mix `@next` Worker with a stable image, never gradual container rollout for this cutover (immediate only — the protocols are incompatible both ways), never treat `await exec` as command completion, and never force production cutover without the user's agreement. By @cloudflare, listed here with credit to its creator. Honest caveats: migration-only — new projects should start on `@next` (the `sandbox-next` skill, not this one) and day-to-day stable work stays on `sandbox-stable`; production cutover is gated on your explicit agreement; needs npm, a matching container image and wrangler. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Cloudflare Sandbox SDK migration to 1.0 preview is a free Muse skill that ports Cloudflare Sandbox apps from stable @cloudflare/sandbox to the 1.0 preview, with an audit, an API replacement map, hard rules and validation, so the migration follows a checked map of what changed, instead of hunting breaking changes one error at a time.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit c430dd9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: an existing app on @cloudflare/sandbox stable that you want to port to the 1.0 preview; npm, wrangler and Docker access; your explicit agreement is required before any production cutover Install "Cloudflare Sandbox SDK migration to 1.0 preview" for me. Give my agent Cloudflare's official workflow for porting Sandbox apps to the @next 1.0 preview — audit, API replacement map, hard rules, code upgrade shapes and validation checklist Repository: https://raw.githubusercontent.com/cloudflare/skills/c430dd965cea3a8faf0ef035e3b3d73b38518081/skills/sandbox-migrate-to-next/SKILL.md Pinned version: install the code at commit c430dd965cea3a8faf0ef035e3b3d73b38518081 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the cloudflare-skills-sandbox-migrate-to-next skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "cloudflare-skills-sandbox-migrate-to-next". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. decide on the production cutover window when the audit is done). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- c430dd9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.