sandbox-check

Detect network and filesystem sandbox constraints across project files.

3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/t6adev/claude-code-tools --skill sandbox-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sandbox-check
Source: https://github.com/t6adev/claude-code-tools/tree/main/tools/skills/infra/sandbox-check
Command: npx skills add https://github.com/t6adev/claude-code-tools --skill sandbox-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code sandbox compatibility validation helps ensure development environments conform to sandbox rules so workflows don't fail unexpectedly.

Core Features & Use Cases

  • Phase 1: Sandbox settings collection from global and project files
  • Phase 2: Development flow discovery from project files
  • Phase 3: Static compatibility checks for network and filesystem
  • Phase 4: (Optional) Execution validation of common commands
  • Phase 5: Comprehensive report generation with actionable recommendations
  • Use Case: Before starting work, validate the project against sandbox constraints to prevent blockers during CI or local runs.

Quick Start

Invoke the sandbox-check skill to pre-validate your project against sandbox constraints and generate a compatibility report.

Frequently Asked Questions about sandbox-check

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

FAQPage Schema
What is sandbox compatibility checking for Claude Code development workflows?

Sandbox compatibility checking scans project files like settings.json, CLAUDE.md, package.json, tests, and CI configs to detect network, filesystem, and local binding constraints that could block commands or cause development workflows to fail unexpectedly.

How do I pre-check my project against sandbox constraints before starting development?

To pre-check your project, invoke a sandbox validation skill that collects settings from global and project files, discovers development flows, performs static compatibility checks, and generates a detailed report with actionable recommendations.

Does sandbox validation work with my existing CI configs and package.json files?

Yes, sandbox compatibility validation works across existing source files by scanning CI configs, package.json, test files, and settings.json to identify constraints that could block commands during local runs or CI pipelines.

Why does my development workflow fail unexpectedly in a sandboxed environment?

Development workflows fail in sandboxed environments when undetected network, filesystem, or local binding constraints block execution. Running a source-wide static compatibility check on project files identifies these blockers before they interrupt your work.

What's the best way to generate a compatibility report for Claude Code sandbox rules?

The best way to generate a compatibility report is to run an automated check that collects sandbox settings, validates static constraints across the project, and produces a final report detailing findings and recommended actions.

Are there limitations to static sandbox compatibility checks for local binding constraints?

Static sandbox compatibility checks identify network and filesystem constraints from project files, but optional execution validation of common commands may be needed to fully verify local binding constraints and prevent runtime blockers.