Install
npx skills add vercel/sandboxWho it's for
Open this Skill when you need to run arbitrary code inside an isolated, ephemeral Linux VM. The official line is: Vercel Sandbox allows you to run arbitrary code in isolated, ephemeral Linux VMs. The repository title says it is for running untrusted or user-generated code safely.
It is not a general compute handbook. The Skill gives code patterns, practice notes, and API reference for the @vercel/sandbox SDK. It fits people who have already chosen Vercel Sandbox and want an agent to gather call points from the official SDK. If the task does not need an isolated VM, this Skill does not match.
Page:
https://github.com/vercel/sandbox
First try in 3 minutes
Take only the official Skill install command. Do not pick another main install path at the same time:
npx skills add vercel/sandbox
Prerequisite: the current task really is “run arbitrary code in an isolated, ephemeral Linux VM,” and the current agent environment can run the npx skills add command above. The official text does not write an install destination directory, so do not invent a path that never appears.
After install, do a read-only check first. Do not create a sandbox and do not change project files. Ask the agent: according to the Sandbox Skill, what can the timeout option of Sandbox.create() configure, and what are the default duration and plan caps. Observable success: the agent states the default is 5 minutes, Hobby max 45 minutes, Pro/Enterprise max 24 hours, and that these durations are adjusted through timeout on Sandbox.create(). If the agent only repeats “it can run code” and cannot give these numbers, it has not used this Skill yet; run the same install command again and ask once more.
Use cases
Case 1: Have the agent gather @vercel/sandbox call points from the Skill. The page writes that the Skill gives comprehensive guidance on using the @vercel/sandbox SDK, including code patterns, best practices, and API reference. Hand the agent “run a piece of arbitrary code in an isolated, ephemeral Linux VM” and ask it to list, from the Skill only, the SDK name and patterns that must be checked at create time, and to mark fields the page does not write. Checkable result: the reply stays around @vercel/sandbox and Sandbox.create(), instead of inventing another install command.
Case 2: Check resources and duration before creating. Official caps: Hobby/Pro up to 8 vCPU, Enterprise up to 32 vCPU, each vCPU corresponding to 2048 MB of memory; sandbox default 5 minutes, Hobby max 45 minutes, Pro/Enterprise max 24 hours, adjustable with timeout. This fits a capacity check before really starting a VM: whether the current task must exceed the default 5 minutes, and whether it will hit Hobby's 45-minute cap. The page gives no console steps or billing actions; the check stops at these numbers.
Boundaries
This is an ephemeral, isolated Linux VM, not a standing host; the page does not promise local files will persist.
Resources written: Hobby/Pro 8 vCPU, Enterprise 32 vCPU, 2048 MB memory per vCPU. Disk, outbound network, and concurrency counts do not appear; do not fill missing items.
Default duration 5 minutes; Hobby max 45 minutes; Pro/Enterprise max 24 hours. The page does not give a method for occupancy beyond that window.
The Skill covers @vercel/sandbox patterns, practices, and API reference. It does not list clients, so do not write that only one agent is supported.
The same page also gives the SDK install command pnpm i @vercel/sandbox. That is SDK package install, not a second Skill main path; on the first try do not place it beside npx skills add vercel/sandbox. The official text does not write other package managers or marketplace installs.
The page does not describe project linking, environment variables, or secret filling; do not invent steps that never appear.