sandbox-verify

Compare local test results with E2B sandbox executions and emit deterministic verdicts.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/paulingham/.claude --skill sandbox-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sandbox-verify
Source: https://github.com/paulingham/.claude/tree/main/skills/sandbox-verify
Command: npx skills add https://github.com/paulingham/.claude --skill sandbox-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate builds by cross-checking the local test results against a remote sandbox, catching divergences early to prevent shipped defects.

Core Features & Use Cases

  • Build-phase gate runs the project tests in a remote sandbox (E2B) alongside the local run and compares per-test outcomes.
  • Verdicts are deterministic: SANDBOX_VERIFIED when passes match, SANDBOX_FAILED when they diverge, SANDBOX_SKIPPED when sandbox is unavailable.
  • Use case: verify that CI or local runs reproduce the same test outcomes in an isolated sandbox to improve reliability and compliance.

Quick Start

After your local tests pass, trigger sandbox-verify to compare per-test results with the sandbox and emit a final verdict.

Frequently Asked Questions about sandbox-verify

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

FAQPage Schema
How do I verify local test results match sandbox execution in CI?

To verify local test results match sandbox execution, trigger a parity check that provisions a remote E2B sandbox, runs the project tests, and compares per-test outcomes to catch cross-environment divergences before deployment.

What is sandbox parity checking for build pipelines?

Sandbox parity checking for build pipelines is the process of cross-checking local test pass sets against remote sandbox executions to ensure cross-environment consistency and gate deployments against reproducible test outcomes.

Do I need an E2B sandbox to run cross-environment parity checks?

Yes, you need an E2B sandbox to run cross-environment parity checks, as the verification process provisions it to execute tests remotely and compare results against your local run for deterministic verdicts.

What verdicts are emitted when comparing local and sandbox test outcomes?

The deterministic verdicts emitted when comparing local and sandbox test outcomes are SANDBOX_VERIFIED when passes match, SANDBOX_FAILED when they diverge, and SANDBOX_SKIPPED when the sandbox is unavailable.

What happens to the build gate if the sandbox is unavailable during verification?

If the sandbox is unavailable during verification, the build gate process emits a SANDBOX_SKIPPED verdict, allowing the pipeline to handle the skipped state without failing the cross-environment consistency check.

Why does my CI pipeline need cross-environment test consistency verification?

Your CI pipeline needs cross-environment test consistency verification to catch divergences between local and isolated sandbox runs early, preventing shipped defects and ensuring reproducible test outcomes for compliance and reliability.