agentleFS
nabchtnabcht/Zephyr/skills/sandbox/SKILL.md

sandbox

Skill2 starsChanged 6 months agoMITView on GitHub

Executes Python code in a temporary sandbox to verify it works before finalizing a mission.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify Logic: Ensure that new algorithms or functions produce the expected output.

    line 15
  2. Distinctive:

    Test Dependencies: Verify if specific third-party requirements function correctly.

    line 17
  3. Distinctive:

    Prevent Loops: Use the built-in 15-second timeout to detect potential infinite loops safely.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

sandbox

Executes a snippet of Python code in an isolated temporary environment. This skill is primarily used by the Coder to verify that a proposed solution or script works as intended before it is delivered to the user or integrated into the core system.

Usage

This skill is used by the Coder to:

  1. Verify Logic: Ensure that new algorithms or functions produce the expected output.
  2. Check Syntax: Validate that generated code is free of syntax errors.
  3. Test Dependencies: Verify if specific third-party requirements function correctly.
  4. Prevent Loops: Use the built-in 15-second timeout to detect potential infinite loops safely.

Important Note

The sandbox can run in two modes:

  1. Docker-backed containment when SANDBOX_BACKEND=docker or auto with Docker available.
  2. A process-isolated fallback when Docker is unavailable.

The Docker path disables container networking and mounts only the temporary workspace. The fallback path still uses subprocess.run, isolated Python startup, a temporary workspace, and a sanitized environment, but it is not equivalent to full container or WASM isolation.

Implementation

The execution logic is contained within scripts/sandbox.py. It captures STDOUT and STDERR to provide a full execution report back to the agent for debugging or confirmation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.