docker-sandboxes-lifecycle

From README

Docker Sandboxes: Local Lifecycle & Workspace Isolation Overview Docker Sandboxes (sbx) runs an AI coding agent inside an isolated microVM with its own filesystem, network, and Docker daemon. This skill owns the local sandbox lifecycle — creating, reattaching to, listing, stopping, and removing sandboxes — and the workspace isolation choice (direct bind mount vs. --clone). It does not cover network policy, credentials, sbxenv.yaml, or kit authoring — see Related skills. When to use this skill Activate this skill when: The user wants to start, reattach to, stop, or remove a local sbx sandbox. The user wants an agent to work on a repository without giving it a writable bind mount of the host working tree (--clone). The user wants extra read-only (or write-restricted) workspaces mounted alongside the primary one. The user is copying files between host and sandbox, publishing a sandbox port, or running an ad-hoc command inside a sandbox (sbx exec).