benchmark-sandbox

Runs vercel-plugin eval scenarios in ephemeral Vercel Sandboxes with build, verify, and deploy phases.

Updated Aug 21, 2025
One-click install
npx skills add https://github.com/Adithiya-S/AI-Study-Companion --skill benchmark-sandbox-adithiya-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark-sandbox
Source: https://github.com/Adithiya-S/AI-Study-Companion/tree/main/.agents/skills/benchmark-sandbox
Command: npx skills add https://github.com/Adithiya-S/AI-Study-Companion --skill benchmark-sandbox-adithiya-s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @vercel/sandbox, @anthropic-ai/claude-code, agent-browser, vercel.

What problem does it solve? Running plugin benchmark evals locally in WezTerm terminal panes limits parallelism, requires manual verification, and leaves no permanent deploy URLs. This Skill moves eval scenarios into ephemeral Vercel Sandbox microVMs so builds, browser verification, and deployments run in parallel with structured scoring. ## Core Features & Use Cases - 3-Phase Eval Pipeline: Phase 1 builds the app with Claude Code, Phase 2 uses agent-browser to verify user stories and fix issues, Phase 3 links to the vercel-labs team and deploys with up to 3 build-error retries. - Structured Haiku Scoring: Each phase is scored via claude -p --json-schema --model haiku, returning structured JSON for build completeness, per-story pass/fail, and deploy success. - Skill Coverage Tracking: Skills injected by the plugin are polled and re-extracted after every phase, producing coverage reports comparing expected vs. claimed skills per scenario. - Use Case: Generate a JSON file of app-building scenarios with user stories, then run run-eval.ts --scenarios-file to execute them across up to 10 parallel sandboxes and get a markdown report with deploy URLs. ## Quick Start Run the benchmark sandbox eval with my scenarios file using bun run .claude/skills/benchmark-sandbox/run-eval.ts --scenarios-file /tmp/my-scenarios.json.

Frequently Asked Questions about benchmark-sandbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run vercel-plugin eval scenarios in Vercel Sandboxes?

Run bun run .claude/skills/benchmark-sandbox/run-eval.ts with an optional --scenarios-file pointing to a JSON array of scenarios. Each scenario needs a slug, prompt, expectedSkills array, and exactly three user stories.

What is the difference between benchmark-sandbox and benchmark-agents?

benchmark-agents runs evals in local macOS WezTerm panes with manual verification, while benchmark-sandbox uses remote Vercel Sandboxes with up to 10 parallel microVMs, automated agent-browser verification, deploy phases, and haiku structured scoring.

Which Vercel Sandbox SDK version works with this eval runner?

Use @vercel/sandbox version 1.8.0. The v2 beta's named sandbox endpoint returns 404 for the vercel-labs team, so it is incompatible with this runner.

Why do sandbox eval artifacts disappear before extraction?

Sandbox filesystems are ephemeral and the session-end-cleanup hook deletes skill claim directories when the session ends. Extract artifacts before the session completes or rely on poll history data, and snapshot after the build phase as a restore point.

Can I keep sandboxes alive after an eval run finishes?

Yes, pass --keep-alive with --keep-hours N to extend sandbox lifetime using sandbox.extendTimeout(). This keeps public https://sb-XXX.vercel.run URLs accessible for manual inspection, such as overnight runs.

How does structured scoring work in the sandbox eval pipeline?

Each phase runs claude -p --json-schema --output-format json --model haiku inside the sandbox to produce structured JSON scores. The actual schema data is in parsed.structured_output, not the top-level response object.