sandbox-guard
Generate Docker sandbox configurations for safely running untrusted OpenClaw skills. Isolates filesystem, network, and process access.
What this skill does
# 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) ```dockerfile FROM node:20-alpine RUN adduser -D -h /workspace openclaw WORKDIR /workspace USER openclaw # No network, no elevated privileges # Mount project as read-only ``` ```bash 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) ```dockerfile FROM node:20-alpine RUN adduser -D -h /workspace openclaw WORKDIR /workspace USER openclaw ``` ```bash 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) ```dockerfile FROM node:20-alpine RUN adduser -D -h /workspace openclaw WORKDIR /workspace USER openclaw ``` ```bash 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
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.