skill-sandbox-configurator

Generate OpenSandbox sandbox configuration and Docker runtime for Agent Skills.

5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/jiluojiluo/agent-skill-sandbox-configurator --skill skill-sandbox-configurator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-sandbox-configurator
Source: https://github.com/jiluojiluo/agent-skill-sandbox-configurator/tree/main
Command: npx skills add https://github.com/jiluojiluo/agent-skill-sandbox-configurator --skill skill-sandbox-configurator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents unsafe or inconsistent execution of Agent Skills by generating a controlled OpenSandbox/Docker environment from an existing skill directory and its declared permission risks.

Core Features & Use Cases

  • Scans Skill permissions and risk signals: analyzes the target skill’s SKILL.md and its Python/Shell/markdown files to identify potential high-risk behaviors (e.g., secret access, deletion, external sending).
  • Generates sandbox assets on demand: creates per-skill sandbox configuration, including sandbox.json, PERMISSIONS.md, a requirements.txt stub based on detected imports, and a sandbox/Dockerfile template.
  • Performs safety-oriented security checks: produces warnings or blocks guidance based on detected CRITICAL/HIGH/MEDIUM patterns, aligning the generated permission level to the observed needs.
  • Updates agent documentation for operational compliance: ensures the project’s AGENTS.md includes a standardized “Sandbox 执行要求” section when missing.
  • Builds a dedicated Docker image: constructs a {skill-name}-sandbox:latest image from the generated sandbox directory and prepares a test run command.

Example use case: You have a community or internal skill that needs to run inside OpenSandbox; use this Skill to generate a least-privilege sandbox setup that denies dangerous filesystem paths, restricts environment variables, and blocks unexpected network/exfiltration behaviors.

Quick Start

Ask the agent to run the sandbox configurator for your skill named contract-legal-review, ensuring it scans the skill, generates sandbox.json and related files, performs security checks, and builds the Docker image.

Frequently Asked Questions about skill-sandbox-configurator

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

FAQPage Schema
How do I generate a Docker sandbox configuration for an existing Agent Skill?

To generate a Docker sandbox configuration, the tool reads your skill's SKILL.md, scans for permission risks, and produces sandbox.json, PERMISSIONS.md, requirements.txt, and a Dockerfile for isolated execution.

What is the best way to isolate risky Agent Skills before running them?

Isolating risky Agent Skills requires generating a restricted Docker runtime that enforces least-privilege access, denies dangerous filesystem paths, and blocks unexpected network exfiltration behaviors based on scanned permissions.

How does permission scanning work for Python and Shell scripts in an Agent Skill?

Permission scanning analyzes target skill Python, Shell, and markdown files to identify potential high-risk behaviors like secret access, deletion, or external sending, then aligns the permission level to observed needs.

Does OpenSandbox support building a dedicated Docker image for community skills?

Yes, OpenSandbox supports building a dedicated Docker image by constructing a {skill-name}-sandbox:latest image from the generated sandbox directory and preparing a test run command for isolated execution.

When do I need to update AGENTS.md for sandbox execution compliance?

You need to update AGENTS.md for sandbox execution compliance when the project documentation is missing a standardized "Sandbox 执行要求" section, ensuring operational compliance for isolated skill execution.

What are the limitations of automated permission level selection for sandbox configurations?

Automated permission level selection is limited by its reliance on static analysis of declared risks, producing warnings or blocks based on detected CRITICAL, HIGH, and MEDIUM patterns without guaranteeing complete runtime safety.