Skip to content

Add stable and @next Sandbox agent skills - #92

Merged
ghostwriternr merged 5 commits into
mainfrom
sandbox-skills-1-0-migration
Aug 7, 2026
Merged

Add stable and @next Sandbox agent skills#92
ghostwriternr merged 5 commits into
mainfrom
sandbox-skills-1-0-migration

Conversation

@ghostwriternr

@ghostwriternr ghostwriternr commented Aug 7, 2026

Copy link
Copy Markdown
Member

Stable @cloudflare/sandbox and @cloudflare/sandbox@next use incompatible command models (buffered string exec vs argv handles). A single product skill teaches agents the wrong contract half the time, and docs-local SKILL.md files sit outside the normal cloudflare/skills install path.

This change puts three skills on the central install path so agents pick the right package first, stay productive on either release during the 1.0 preview window, and only port when asked:

  • sandbox-next — build on @next (recommended for new projects)
  • sandbox-stable — build on the current stable package
  • sandbox-migrate-to-next — perform stable → @next when upgrading

Build skills are gates and retrieval maps (package check, non-negotiable contract, task → docs), not full API manuals. Migrate is a stepwise runbook. Optional @next reference files are explicit cheatsheets; exhaustive signatures stay in installed types and developers.cloudflare.com.

Companion docs PR wires the same skill names into Sandbox coding-agent blurbs: cloudflare/cloudflare-docs#32291

Test plan:

  • Install via Agent setup / npx skills add https://github.com/cloudflare/skills and confirm the three skill names appear
  • On a stable app, agent loads sandbox-stable (or stops if it opened sandbox-next) and does not rewrite to argv/output() handles
  • On an @next app, agent uses argv exec and does not assume command completion at await exec
  • “Migrate to 1.0” loads sandbox-migrate-to-next and does not force production cutover without asking

Refresh sandbox-sdk for @next and add sandbox-v1-migration plus
sandbox-2026-deprecation so agents install migrate paths from
cloudflare/skills instead of docs-only markdown.
@ghostwriternr
ghostwriternr marked this pull request as draft August 7, 2026 15:58
Agents need separate build paths for stable and @next so they do
not mix incompatible exec models. Keep migration as its own
performable upgrade skill.
Pair build skills as sandbox-next and sandbox-stable so the
package line is obvious from the skill name.
Build skills gate the package line, state the contract, and
route to docs by task. Keep migrate as a stepwise port runbook.
Point exhaustive reading at types and docs so agents do not
treat the process/terminal stub as the full Sandbox surface.
@ghostwriternr ghostwriternr changed the title Add Sandbox 1.0 migration skills Add package-line Sandbox agent skills Aug 7, 2026
@ghostwriternr ghostwriternr changed the title Add package-line Sandbox agent skills Add stable and @next Sandbox agent skills Aug 7, 2026
@ghostwriternr
ghostwriternr marked this pull request as ready for review August 7, 2026 16:50
@ghostwriternr
ghostwriternr merged commit f96bff7 into main Aug 7, 2026
3 checks passed
@ghostwriternr
ghostwriternr deleted the sandbox-skills-1-0-migration branch August 7, 2026 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant