CtrlK
BlogDocsLog inGet started
Tessl Logo

sandbox-bridge

Use when you need to exercise a real, running Sandbox deployment via HTTP — for example to validate SDK changes against a live container, reproduce a user-reported issue, or experiment with the API (including FUSE bucket mounts) without spinning up `wrangler dev`. Documents the Sandbox bridge worker reachable via `SANDBOX_WORKER_URL` + `SANDBOX_API_KEY` when the host injects them.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, actionable reference with copy-paste commands covering the full sandbox lifecycle and good deferral of exhaustive detail to the OpenAPI spec. Workflow sequencing is clear but could add explicit validation checkpoints before destructive/cleanup steps.

Suggestions

Add an explicit validation checkpoint in the Typical Flow (e.g. verify `$SID` is non-empty after creation, and check the exec `exit` event before proceeding) to lift workflow clarity.

Tighten the Sessions rationale prose; the two-bullet isolation list already conveys the key points without the surrounding justification.

Consider splitting the endpoint/error reference tables into a short bundled reference file so the SKILL.md body stays a lean overview, improving progressive disclosure further.

DimensionReasoningScore

Conciseness

Largely efficient reference prose backed by concrete curl commands, with minimal over-explanation of concepts Claude already knows; a few explanatory passages (e.g. the sessions rationale) could be tightened slightly.

4 / 5

Actionability

Fully executable, copy-paste-ready curl commands for every common case (create, exec via SSE, file read/write, destroy, sessions), plus a decoded-stdout helper and concrete env-var/header usage.

5 / 5

Workflow Clarity

A clear numbered Typical Flow (create → exec → read/write → destroy) with the cleanup step emphasized and error/exit-event handling explained, though explicit pre-step validation checkpoints (e.g. verify SID non-empty) are only implicit.

4 / 5

Progressive Disclosure

Well-organized into labeled sections and defers bulk schema detail to the bridge's own '/v1/openapi.json' (one level deep, clearly signaled); no bundle files exist, and the single-file layout is reasonable for this reference skill.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both capability and trigger conditions with concrete use cases. It is well-distinguished from sibling skills; only minor synonym coverage is missing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'exercise a real, running Sandbox deployment via HTTP', 'validate SDK changes against a live container', 'reproduce a user-reported issue', 'experiment with the API (including FUSE bucket mounts)' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what ('exercise a real, running Sandbox deployment via HTTP', 'Documents the Sandbox bridge worker reachable via SANDBOX_WORKER_URL + SANDBOX_API_KEY') and when ('Use when you need to...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-phrasing coverage ('validate SDK changes', 'reproduce a user-reported issue', 'experiment with the API', 'FUSE bucket mounts', 'wrangler dev'), but a few common variations a user might say (e.g. 'test against a live sandbox', 'debug the sandbox') are not present.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (the Sandbox bridge worker over HTTP with specific env vars) and even contrasts against 'wrangler dev', minimizing conflict risk with adjacent skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
cloudflare/sandbox-sdk
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.