CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

offload-to-sandbox

Offload heavy builds, full test suites and parallel experiments from the local machine to Vercel Sandboxes with the `vercel sandbox` CLI. Use when a local machine is overloaded or shared by several agents, when a test suite should be sharded, or when many tasks should run side by side without consuming local CPU, memory or disk.

Quality

90%

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

85%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 highly actionable, well-sequenced operational guide: executable commands throughout, a complete wrapper script, explicit validation checkpoints, and a strong pitfalls section. Its main weakness is structure, not substance — everything lives inline in one long SKILL.md with no scripts/ or references/ split, and CLI-version-specific detail is woven into the main flow rather than isolated.

Suggestions

Move the full `sbx` wrapper script to `scripts/sbx` and reference it with a short usage summary, keeping the SKILL.md body focused on the workflow and decision points.

Extract the standalone-CLI sections (file read/write/copy, long-job command management, stdin piping, older-CLI fallbacks) into a `references/` file (e.g. `standalone-cli.md`) linked from a brief pointer in the main body.

Consolidate version-sensitive details (`vercel` 64.5.0 / Sandbox CLI 4.4.0 exit-code bug, vercel/sandbox#380 support check) into a single 'CLI version compatibility' or deprecated-behaviors section so the main flow stays version-agnostic and ages better.

DimensionReasoningScore

Conciseness

The body is dense and operational with almost no teaching of known concepts, matching anchor 4's "efficient; minor instances of over-explanation". Not 5 because time-sensitive version pins ("With `vercel` 64.5.0 (Sandbox CLI 4.4.0)", "vercel/sandbox#380") sit in main sections rather than an old-patterns/deprecated section, and a few rationale sentences could be trimmed; not 3 because there is no substantial unnecessary explanation.

4 / 5

Actionability

Every phase has copy-paste-ready commands ("vercel sandbox create --name exp-parser --non-persistent --snapshot ...", "sandbox read --scope ...", the full `sbx` wrapper script with usage messages and error handling) and a worked "Typical agent session" covers the common cases — a direct anchor-5 match.

5 / 5

Workflow Clarity

The sections follow the real sequence (snapshot → create → push → run → results → remove) with explicit validation checkpoints and feedback loops: "Check that step 2 printed `exit=0` before you snapshot", "test -s BASE_SNAPSHOT", checking the snapshot still shows status `created`, the exit-status fallback for exec, `sbx get` verifying the copied file exists, baseline comparison to isolate new failures, and a Pitfalls section with recovery guidance (137/OOM, session timeout). This matches anchor 5, including for the destructive/batch operations (remove/clean) which have explicit guardrails ("Sweep the whole project ... only when no agent is still working").

5 / 5

Progressive Disclosure

The skill is a ~370-line monolith with no bundle files at all: the 110-line `sbx` wrapper belongs in `scripts/`, and the standalone-CLI file-transfer and long-job command-management details belong in a `references/` file. Header structure and internal anchors are good (above anchor 2), but "content that should be separate is inline" lands it on anchor 3 rather than 4.

3 / 5

Total

17

/

20

Passed

Description

95%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 a strong exemplar: it states concrete capabilities with the exact tool, then gives an explicit 'Use when' clause rich in natural trigger phrases covering the overloaded-machine, multi-agent, and sharding scenarios. Voice is correct (no first/second person) and conflict risk is minimal given the tool-specific framing. The only nit is that capability coverage is narrower than the skill's full scope (snapshotting, file transfer, and cleanup are absent).

DimensionReasoningScore

Specificity

"Offload heavy builds, full test suites and parallel experiments... with the `vercel sandbox` CLI" names the tool and three concrete workloads, matching anchor 4's "several specific actions; minor gaps". Not 5 because it is one verb applied to three workloads and omits capabilities the body covers (snapshotting, file transfer, cleanup); not 3 because it clearly lists multiple specific actions rather than 1-2.

4 / 5

Completeness

The first sentence explicitly states what the skill does and "Use when a local machine is overloaded or shared by several agents, when a test suite should be sharded..." gives concrete trigger conditions, exactly matching the anchor-5 example structure. Not 4 because the 'when' clause is already explicit and specific, not merely present.

5 / 5

Trigger Term Quality

"a local machine is overloaded or shared by several agents", "a test suite should be sharded", "many tasks should run side by side without consuming local CPU, memory or disk" comprehensively covers the natural phrases and synonyms a user would say when needing this skill, matching anchor 5.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — offloading to "Vercel Sandboxes with the `vercel sandbox` CLI" — and the triggers (overloaded/shared machine, sharding, parallel offload) would not fire for unrelated skills, giving minimal conflict risk per anchor 5.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

vercel/vercel-plugin

Path

skills/offload-to-sandbox/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.