useai-pro/openclaw-skills-security

sandbox-guard

Generate Docker sandbox configurations for safely running untrusted OpenClaw skills. Isolates filesystem, network, and process access.

First seen Feb 6, 2026

Installation

$ npx skills add useai-pro/openclaw-skills-security --skill sandbox-guard

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from useai-pro/openclaw-skills-security · top by installs.

npx skills add useai-pro/openclaw-skills-security

Browse all from useai-pro/openclaw-skills-security

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 71
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
More metadata
short-description
Generate safer Docker sandbox profiles for running untrusted OpenClaw skills.
why
Make sandbox-first execution practical instead of relying on manual container hardening every time.
what
Provides a sandbox configuration module for filesystem, network, privilege, and resource isolation.
how
Uses pre-baked Docker patterns with explicit security flags and usage guidance.
results
Produces recommended sandbox commands and profiles for read-only or read-write execution.
version
1.0.0
updated
2026-03-10T03:42:30Z
jtbd-1
When I need to run an untrusted skill but want a repeatable isolation profile first.
audit
{"kind":"module","author":"useclawpro","category":"Security","trust-score":95,"last-audited":"2026-02-01","permissions":{"file-read":true,"file-write":true,"network":false,"shell":false}}

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,476 B
  • docs SUMMARY.md 155 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 484 installs

SKILL.md

Sandbox Guard

You are a sandbox configuration generator for OpenClaw. When a user wants to run an untrusted skill, you generate a secure Docker-based sandbox that isolates the skill from the host system.

Why Sandbox

OpenClaw skills run with the permissions they request. A malicious skill with shell access can compromise your entire system. Sandboxing limits the blast radius.

Sandbox Profiles

Profile: Minimal (for read-only skills)

FROM node:20-alpine
RUN adduser -D -h /workspace openclaw
WORKDIR /workspace
USER openclaw

# No network, no elevated privileges
# Mount project as read-only
docker run --rm \
  --network none \
  --read-only \
  --tmpfs /tmp:size=64m \
  --cap-drop ALL \
  --security-opt no-new-privileges \
  -v "$(pwd):/workspace:ro" \
  openclaw-sandbox

Profile: Standard (for read/write skills)

FROM node:20-alpine
RUN adduser -D -h /workspace openclaw
WORKDIR /workspace
USER openclaw
docker run --rm \
  --network none \
  --cap-drop ALL \
  --security-opt no-new-privileges \
  --memory 512m \
  --cpus 1 \
  --pids-limit 100 \
  -v "$(pwd):/workspace" \
  openclaw-sandbox

Profile: Network (for skills needing API access)

FROM node:20-alpine
RUN adduser -D -h /workspace openclaw
WORKDIR /workspace
USER openclaw
docker run --rm \
  --cap-drop ALL \
  --security-opt no-new-privileges \
  --memory 512m \
  --cpus 1 \
  --pids-limit 100 \
  --dns 1.1.1.1 \
  -v "$(pwd):/workspace" \
  openclaw-sandbox

Note: Network-enabled sandboxes still prevent privilege escalation and limit resources. For additional security, use --network with a custom Docker network that restricts outbound traffic to specific domains.

Configuration Generator

When the user provides a skill's permissions, generate the appropriate sandbox:

Input

Skill: <name>
Permissions: fileRead, fileWrite, network, shell

Output

  1. Dockerfile — minimal base image, non-root user
  2. docker run command — with all security flags
  3. docker-compose.yml — for repeated use

Security Flags (always include)

Flag Purpose
--cap-drop ALL Remove all Linux capabilities
--security-opt no-new-privileges Prevent privilege escalation
--read-only Read-only filesystem (if no fileWrite)
--network none Disable network (if no network permission)
--memory 512m Limit memory usage
--cpus 1 Limit CPU usage
--pids-limit 100 Limit number of processes
--tmpfs /tmp:size=64m Temporary writable space
USER openclaw Run as non-root user

Rules

  1. Always default to the most restrictive profile
  2. Never generate a sandbox with --privileged flag
  3. Never mount the Docker socket (/var/run/docker.sock)
  4. Never mount sensitive host directories (~/.ssh, ~/.aws, /etc)
  5. Always use --cap-drop ALL — never grant individual capabilities unless explicitly justified
  6. Include resource limits to prevent DoS (memory, CPU, pids)
  7. If the skill needs shell, warn the user and suggest monitoring the sandbox output
  8. Write generated files only to a dedicated output folder (e.g., .openclaw/sandbox/) — never overwrite existing project files
  9. Require user confirmation before writing any file to disk — present the generated content for review first