/SKILL.md
--- name: docker-socket-proxy description: Manage a remote Docker host via a Tecnativa docker-socket-proxy instance. Unlike raw Docker socket access (which is root-equivalent), docker-socket-proxy acts as a firewall: each API section is individually enabled or disabled via env vars, so the agent only gets access to what you explicitly allow. Requires docker-socket-proxy exposed over TCP. Covers the full Docker REST API surface: container lifecycle (list, start, stop, restart, kill, pause, unpaus
npx skillsauth add BP602/docker-socket-proxy docker-socket-proxyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manages Docker containers via the tecnativa/docker-socket-proxy REST API using curl and jq. Which modes are available depends on which API sections the proxy instance has enabled.
bash {baseDir}/scripts/run-docker.sh <mode> [args...]
Run with no arguments for full usage. Proxy URL is resolved from $DOCKER_PROXY_URL → $DOCKER_HOST (tcp→http) → http://localhost:2375.
| Mode | Description |
|------|-------------|
| ping | Health check |
| version | Docker version |
| info | Host summary (containers, memory, etc.) |
| events [--since T] [--until T] [--filters k=v] | Recent events (1s window) |
| system-df | Disk usage by images/containers/volumes |
| Mode | Description |
|------|-------------|
| list | Running containers |
| list-all | All containers including stopped |
| inspect <name> | Full container details |
| top <name> [ps-args] | Running processes inside container |
| logs <name> [tail] | Container logs (default tail=100) |
| stats <name> | CPU, memory, network, block I/O |
| changes <name> | Filesystem changes since start |
| start <name> | Start container |
| stop <name> [timeout] | Stop container |
| restart <name> [timeout] | Restart container |
| kill <name> [signal] | Kill container (default SIGKILL) |
| pause <name> | Pause container |
| unpause <name> | Unpause container |
| rename <name> <new-name> | Rename container |
| exec <name> <cmd> [args...] | Run command in container |
| prune-containers | Remove stopped containers |
| Mode | Description |
|------|-------------|
| images | List images |
| image-inspect <name> | Image details |
| image-history <name> | Layer history |
| prune-images | Remove unused images |
| Mode | Description |
|------|-------------|
| networks | List networks |
| network-inspect <name> | Network details and connected containers |
| prune-networks | Remove unused networks |
| Mode | Description |
|------|-------------|
| volumes | List volumes |
| volume-inspect <name> | Volume details |
| prune-volumes | Remove unused volumes |
| Mode | Description |
|------|-------------|
| swarm | Swarm info |
| nodes | List nodes |
| node-inspect <name> | Node details |
| services | List services |
| service-inspect <name> | Service details |
| service-logs <name> [tail] | Service logs |
| tasks | List tasks |
| configs | List configs |
| secrets | List secrets |
| Mode | Description |
|------|-------------|
| plugins | List plugins |
Container names can be partial — myapp matches project-myapp-1. Exact match is tried first, then substring. Errors clearly if 0 or 2+ containers match.
IMAGES, NETWORKS, VOLUMES, SYSTEM) will return HTTP 403. This is expected — enable the relevant env var on the proxy to unlock them.exec is two-step (create + start) and streams multiplexed output.events uses a 1-second window by default; use --since / --until to adjust.development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.