Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Test untrusted skills in an isolated environment before installing. Monitors network access, filesystem writes, environment variable reads, and subprocess ca...
Test untrusted skills in an isolated environment before installing. Monitors network access, filesystem writes, environment variable reads, and subprocess ca...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Run untrusted skills in a monitored environment. See exactly what they do before giving them access to your real system.
ClawHub has hundreds of skills. Some are malicious. Even after scanning with arc-skill-scanner, you can't catch everything with static analysis. The sandbox lets you run a skill's scripts and observe their behavior at runtime โ what network calls they make, what files they access, what environment variables they read.
python3 {baseDir}/scripts/sandbox.py run --path ~/.openclaw/skills/some-skill/
python3 {baseDir}/scripts/sandbox.py run --script ~/.openclaw/skills/some-skill/scripts/main.py
python3 {baseDir}/scripts/sandbox.py run --path ~/.openclaw/skills/some-skill/ --monitor-network
python3 {baseDir}/scripts/sandbox.py run --path ~/.openclaw/skills/some-skill/ --fake-env
python3 {baseDir}/scripts/sandbox.py run --path ~/.openclaw/skills/some-skill/ --timeout 30
python3 {baseDir}/scripts/sandbox.py report --path ~/.openclaw/skills/some-skill/
Files opened (read/write) Directories created File deletions Permission changes
Which env vars are read Whether sensitive keys are accessed (API keys, tokens, passwords) Option to inject fake values to see what the skill does with them
Outbound HTTP/HTTPS requests (URLs, methods, payloads) DNS lookups Socket connections FTP, SMTP, and other protocols
Subprocess calls Shell commands Dynamic imports
observe (default) โ Run the skill and log everything it does. No restrictions. restricted โ Block network access and filesystem writes outside a temp directory. honeypot โ Provide fake credentials and endpoints to see if the skill tries to exfiltrate.
The sandbox produces a JSON report with: All filesystem operations (reads, writes, deletes) All environment variable accesses All network connections attempted All subprocess calls Warnings for suspicious patterns A safety verdict (SAFE / SUSPICIOUS / DANGEROUS)
Combine with the workflow orchestrator for automated pre-install checks: scan skill โ sandbox run โ review report โ install if safe โ audit log
Python skills only (JavaScript/shell support planned) Cannot catch all evasion techniques (obfuscated or delayed execution) Network monitoring requires the skill to use standard Python libraries Not a true OS-level sandbox (use Docker for that level of isolation)
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.