New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Add Sandbox Provider

by computesdk in computesdk/benchmarks

Prep a new sandbox provider for the ComputeSDK benchmarks (wire up the dependency, env var, providers list, and CI workflow).

MITAuto-check passed

Install Add Sandbox Provider

skills CLI
$ npx skills add computesdk/benchmarks --skill add-sandbox-provider -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install computesdk/benchmarks add-sandbox-provider --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/computesdk/benchmarks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/add-sandbox-provider .claude/skills/add-sandbox-provider && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
add-sandbox-provider
GitHub stars
126
Token cost
~1.1k tokens
SKILL.md length
455 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Prep a new sandbox provider for the ComputeSDK benchmarks (wire up the dependency, env var, providers list, and CI workflow).

  • Works in 5 steps: Verify the package and its factory shape → Add the dependency → Document the env var(s) → …
  • Stage a new sandbox/compute provider — e.g
  • SKILL.md covers 1. Verify the package and its…, 2. Add the dependency, 3. Document the env var(s) and 4. Stage the provider entry…, plus 5 more sections
  • Calls npm, git and pnpm

What it does

Add Sandbox Provider is an agent skill from computesdk/benchmarks. Prep a new sandbox provider for the ComputeSDK benchmarks (wire up the dependency, env var, providers list, and CI workflow). Use when asked to add, onboard, or stage a new sandbox/compute provider — e.g. "add provider X", "onboard the foo sandbox", "set up bar for benchmarks".

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with npm. The repository describes itself as: Compare performance across sandbox, storage, browsers, and ai gateway providers. The licence is MIT.

When your agent uses it

  • Stage a new sandbox/compute provider — e.g

Example prompts

  • “add provider X”
  • “onboard the foo sandbox”
  • “set up bar for benchmarks”
  • “/add-sandbox-provider”

Requirements

  • A credential in FOO_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Verify the package and its factory shape
  2. Add the dependency
  3. Document the env var(s)
  4. Stage the provider entry (commented)
  5. Stage the CI workflow (commented)

What it can do on your machine

Read from SKILL.md and the folder at commit 6983ce0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • git
    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, git and pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Add Sandbox Provider loads about 1.1k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 455 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from computesdk/benchmarks at commit 6983ce0, republished under its MIT licence (© computesdk). 455 words, ~1,124 tokens.

Download SKILL.mdSave it as .claude/skills/add-sandbox-provider/SKILL.md (or your agent's skills folder).
name
add-sandbox-provider
description
Prep a new sandbox provider for the ComputeSDK benchmarks (wire up the dependency, env var, providers list, and CI workflow). Use when asked to add, onboard, or stage a new sandbox/compute provider — e.g. "add provider X", "onboard the foo sandbox", "set up bar for benchmarks".

Add a sandbox provider to the benchmarks

This repo benchmarks ComputeSDK sandbox providers. A provider is wired across four files. New providers are staged (every change commented out) until the provider's API secret exists as a GitHub repo secret — then they're activated by uncommenting. The beam provider is the reference example of a staged provider.

Inputs you need from the user (ask if missing): the provider name (lowercase, as it appears on npm @computesdk/<name>) and the env var(s) it authenticates with (e.g. FOO_API_KEY).

1. Verify the package and its factory shape

Never guess the factory name or config keys — confirm against the published package:

bash
npm view @computesdk/<name> version          # confirm it exists, get the version
cd /tmp && npm pack @computesdk/<name>        # then inspect the type defs:
tar -xzf computesdk-<name>-*.tgz -O package/dist/index.d.ts | grep -nE 'declare const|Config|export'

Note the exported factory (usually <name>) and its config interface — which key holds the API key, and whether the key falls back to an env var. Most factories take { apiKey }; some take { token }, { token, workspace }, etc.

2. Add the dependency

In package.json add "@computesdk/<name>": "^<version>" to dependencies, in alphabetical order. Then sync the lockfile:

bash
pnpm install

Confirm the diff only added the new package — git diff --stat package-lock.json (npm may report removing/changing packages while reconciling node_modules on disk; that's fine as long as the committed lockfile only gained the new entry).

3. Document the env var(s)

In benchmarks/.env.example append a section (staged providers live near the bottom, by BEAM):

######### <NAME> ########
<NAME>_API_KEY=your_<name>_api_key

4. Stage the provider entry (commented)

In benchmarks/sandbox/providers.ts:

  • Add a commented import near the other imports: // import { <name> } from '@computesdk/<name>';
  • Add a commented entry in the providers[] array (direct-mode section, alphabetical):
ts
// {
//   name: '<name>',
//   requiredEnvVars: ['<NAME>_API_KEY'],
//   createCompute: () => <name>({ apiKey: process.env.<NAME>_API_KEY! }),
// },

Keep the entry minimal — only name, requiredEnvVars, createCompute. Do NOT copy sandboxOptions, destroyTimeoutMs, etc. from a neighboring provider; those are provider-specific (e.g. autoStopInterval is Daytona-only). Add an option only if the factory's own config documents it.

Show full SKILL.md (177 more words)Show less

5. Stage the CI workflow (commented)

In .github/workflows/sandbox-benchmarks.yml, two spots, both commented like the beam lines:

  • The matrix.provider list: # - <name>
  • The Run benchmark step's env: block: # <NAME>_API_KEY: ${{ secrets.<NAME>_API_KEY }}

What you do NOT need to touch

  • A bench:<name> script in package.json is optional; CI invokes --provider ${{ matrix.provider }} directly. Skip it unless asked.
  • No tests enumerate providers.

Why staged (and why it's safe to activate later)

The runner gracefully skips any provider whose requiredEnvVars are missing — it returns a skipped: true result rather than failing (see benchmarks/sandbox/benchmark.ts, the missingVars check). So activating without the secret wouldn't break CI; staging is a convention to keep the provider list reflecting what's actually being benchmarked until the secret is added.

Activation (later, once the repo secret exists)

Uncomment all four staged blocks: the import and providers[] entry in providers.ts, the matrix line, and the workflow env: line. Add the <NAME>_API_KEY secret in the repo settings first.

Final check

Run git diff and confirm the change set is exactly: package.json, package-lock.json, benchmarks/.env.example, benchmarks/sandbox/providers.ts, .github/workflows/sandbox-benchmarks.yml — and that every provider-specific line is commented out (staged).

© computesdk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/add-sandbox-provider of computesdk/benchmarks.

Open the folder on GitHubat commit 6983ce0

Compare with similar skills

Add Sandbox Provider next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Add Sandbox Provider compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Sandbox Provider this skillcomputesdk/benchmarks126—~1.1kAutomated safety check: PassMIT
Defuddlekepano/obsidian-skills49k11 repos~208Automated safety check: PassMIT
Vercel Deploybytedance/deer-flow84k10 repos~797Automated safety check: PassMIT
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
Knap Markdown Templateskepano/obsidian-skills49k2 repos~986Automated safety check: PassMIT
Nx Run Tasksnomcopter/react-mosaic4.8k8 repos~613Automated safety check: PassCustom licence

Similar skills

  • Defuddle

    kepano/obsidian-skills

    Uses the Defuddle CLI to pull clean, readable Markdown, JSON or metadata from web pages, stripping navigation, ads and clutter to save tokens.

    49k GitHub starsUsed in 11 repos~208 tokens
    Knowledge ManagementAuto-check passed

  • Vercel Deploy

    bytedance/deer-flow

    Deploys a project to Vercel with one script and no login, then returns a live preview URL and a claim link for moving the deployment into your own Vercel account.

    84k GitHub starsUsed in 10 repos~797 tokens
    DevOps & CloudAuto-check passed

  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • Knap Markdown Templates

    kepano/obsidian-skills

    Renders Markdown notes from Knap templates and JSON data on the command line, including notes built from Defuddle web page output.

    49k GitHub starsUsed in 2 repos~986 tokens
    Documents & OfficeAuto-check passed

  • Nx Run Tasks

    nomcopter/react-mosaic

    Helps with running tasks in an Nx workspace. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 8 repos~613 tokens
    DevelopmentAuto-check passed

  • OpenHarness End-to-End Evals

    HKUDS/OpenHarness

    Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.

    16k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check: notes

More from computesdk/benchmarks

  • Local Platform E2E

    computesdk/benchmarks

    Stand up benchmarks-platform locally (Postgres + MinIO + ClickHouse in docker) and run a real @benchsdk/runner benchmark against it, with no cloud or provider credentials.

    126 GitHub stars~3k tokensUpdated today
    Auto-check: notes

  • Writing Benchmarks

    computesdk/benchmarks

    Author or improve a ComputeSDK benchmark. An agent skill from computesdk/benchmarks.

    126 GitHub stars~2.1k tokensUpdated today
    Auto-check: notes

  • Benchsdk CLI

    computesdk/benchmarks

    Install, authenticate, and use the unified bench CLI to query and run ComputeSDK benchmarks.

    126 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Works with

Questions about Add Sandbox Provider

What does Add Sandbox Provider do?

Prep a new sandbox provider for the ComputeSDK benchmarks (wire up the dependency, env var, providers list, and CI workflow). Add Sandbox Provider is an agent skill from computesdk/benchmarks. Prep a new sandbox provider for the ComputeSDK benchmarks (wire up the dependency, env var, providers list, and CI workflow).

When should I use Add Sandbox Provider?

Add Sandbox Provider fits situations like: stage a new sandbox/compute provider — e.g.

How do I install Add Sandbox Provider in Claude Code?

Run `npx skills add computesdk/benchmarks --skill add-sandbox-provider -a claude-code`. Or copy the skill folder (.claude/skills/add-sandbox-provider in computesdk/benchmarks) into .claude/skills/add-sandbox-provider in your project. Claude Code loads it when a task matches its description.

How do I install Add Sandbox Provider in Codex?

Run `npx skills add computesdk/benchmarks --skill add-sandbox-provider -a codex`. Or copy the skill folder (.claude/skills/add-sandbox-provider in computesdk/benchmarks) into .agents/skills/add-sandbox-provider in your project. Codex loads it when a task matches its description.

Can I use Add Sandbox Provider in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add computesdk/benchmarks --skill add-sandbox-provider -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-sandbox-provider, .gemini/skills/add-sandbox-provider, .github/skills/add-sandbox-provider and .opencode/skills/add-sandbox-provider in your project.

What does Add Sandbox Provider need to run?

Going by SKILL.md and its folder, Add Sandbox Provider needs the command-line tools its instructions call (npm, git and pnpm). Our summary lists: A credential in FOO_API_KEY.

Does Add Sandbox Provider access the network?

SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Add Sandbox Provider safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Add Sandbox Provider use?

Add Sandbox Provider is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Add Sandbox Provider use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Add Sandbox Provider?

Skills that share tags, products or a category with Add Sandbox Provider: Defuddle (kepano/obsidian-skills, 49k stars), Vercel Deploy (bytedance/deer-flow, 84k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars) and Knap Markdown Templates (kepano/obsidian-skills, 49k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Sandbox Provider?

computesdk (a GitHub organization) maintains it in computesdk/benchmarks, which has 126 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 9, 2026.

Source: computesdk/benchmarks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.