CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sandbox-next

Build or maintain Cloudflare Sandbox apps on @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-migrate-to-next when porting a stable app.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

This is a strong retrieval-map-style skill: lean, concrete, and well-structured, with a real validation gate up front and an accurate pre-ship checklist. The only weakness is the absence of an explicit in-body error-recovery loop, which is instead correctly delegated to the Errors documentation.

DimensionReasoningScore

Conciseness

The body is dense and lean throughout — gate tables, contract bullets, and a retrieval map with zero explanation of concepts Claude already knows; every line carries API facts or routing decisions, matching the "every token earns its place" anchor.

5 / 5

Actionability

The "Minimal shape" snippet is copy-paste ready and the contract gives exact executable specifics (argv list, ["/bin/bash", "-lc", script], handle method names, null/[] return behavior, pre-ship checks), covering the common exec-and-collect case completely.

5 / 5

Workflow Clarity

The Gate → Contract → Retrieve → Before-you-ship sequence is clear with real checkpoints (package-line inspection before coding, typecheck/lockfile checklist at the end), but there is no explicit error-recovery feedback loop in the body — errors are delegated to the Errors docs — leaving minor validation gaps versus the anchor 5 example.

4 / 5

Progressive Disclosure

The body is a genuine overview that clearly signals exactly the three real bundle files (references/api-quick-ref.md, references/examples.md, references/skill-feedback.md), all of which exist and are one level deep with no nested references — matching the well-signaled one-level-deep anchor.

5 / 5

Total

19

/

20

Passed

Description

65%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.

The description is highly distinctive and precise about its package line, but it lacks an explicit trigger clause for this skill itself — the one "Use when" present points to a sibling skill — and describes only two concrete actions. Adding a "Use when working with @cloudflare/sandbox@next…" clause would resolve the main gap.

Suggestions

Add an explicit trigger clause for this skill, e.g. "Use when the project depends on @cloudflare/sandbox@next or when the user mentions the Sandbox 1.0 preview / @next line."

Name one or two more concrete capabilities in the description (e.g. running commands in isolated Linux environments, interactive terminals, code interpreter) to strengthen the 'what'.

Include natural synonyms users might say — "Cloudflare Containers", "migrate", "sandbox SDK" — to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Build or maintain Cloudflare Sandbox apps on @cloudflare/sandbox@next (SDK 1.0 preview)" names the domain precisely but lists only two actions ("Build or maintain"), matching the 1-2-concrete-actions anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

The "what" is clear (build/maintain apps on the @next preview line), but the only explicit "Use when"-style clause ("Use sandbox-migrate-to-next when porting a stable app") routes to a different skill; when to use this skill itself is only weakly implied, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present — "Cloudflare Sandbox", "@cloudflare/sandbox@next", "SDK 1.0 preview", "porting a stable app" — but common variations like "Cloudflare Containers", "migrate", or "code interpreter" are missing, so it sits at good-but-not-comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Pinning to "@cloudflare/sandbox@next (SDK 1.0 preview)" plus explicit routing away from "sandbox-migrate-to-next" for porting gives a clear niche with minimal conflict risk against sibling skills.

5 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

cloudflare/skills

Path

skills/sandbox-next/SKILL.md

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.