← Explore all skills

SANDBOX CONFIGURATION / Docker

Docker Sandboxes environment file

Pins Docker's sbxenv skill, which treats sbx env plan as a no-change preview and will not default to auto-approving host lifecycle commands.

“Use this skill when authoring, planning, or running a declarative `sbxenv.yaml` file for Docker Sandboxes (`sbx env create/run/plan/exec/rm`), even if the user just says they want to "check in a sandbox config", "make onboarding reproducible for a sandbox", "run a setup script before the agent starts", or "define arguments for a shared sandbox environment". Covers the sbxenv.yaml schema (schemaVersion, agent, kits, workspace/additionalWorkspaces, args, env, secrets, registries, bindings, mcp, ports, sandboxOptions), host `lifecycle:` commands (initialize/postCreate/preRemove) and their approval-plan model, multi-file merge (`-f`-style deep merge and the user-level `.sbxenv.yaml` base layer), and file-write-protection (`sandboxOptions.writableEnvFiles`).”

01 / THE REASONING

Why this made the selection.

  • sbx env plan is described as printing the apply set and changing nothing, while create and run require approval before they do any work. The file says never to default to -y for a file or kit that has not been reviewed.
  • Lifecycle commands run on the host with the operator's privileges. A failing preRemove does not itself block removal, but a new credential, a changed binding, or a replacement sandbox stops removal before deletion.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • skills/docker-sandboxes-env/SKILL.md
  • README.md
  • LICENSE

Our findings

  • sbx env plan prints what applying the file would set up and changes nothing. create and run show that plan and require approval before doing work.
  • The file says never to default to -y for an unreviewed file or kit, and never to treat an untrusted kit's lifecycle commands as pre-approved.
  • Lifecycle commands run on the host, outside the sandbox, with the operator's own privileges. initialize must be idempotent because it reruns on every create and run, including an attach.
  • A failing preRemove does not itself block removal. A new credential, a changed binding not covered by the approval, or a replacement sandbox under the same name stops removal before deletion.
  • A literal secret must not be written into a checked-in sbxenv.yaml. bindings stay after sbx env rm unless --prune-bindings is passed.
  • sbx env exec runs no lifecycle commands and does not create a sandbox. Setting writableEnvFiles true is described as a security downgrade.

Not established by this review

  • The resource was not executed and its tools were not called.
  • sbx env plan, create, run, exec, and rm were not run.
  • No secret was stored, no host lifecycle command was approved, and the verification runbook was not opened.
  • Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Add a skill to your workflow.

Upstream setup instructions ↗

DOCUMENTED COMMAND

npx skills add docker/skills

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

  1. The repository README shows `npx skills add docker/skills` as the skills CLI quick start. It says the command prompts for which skills and which agents, so it does not install this file by itself.
  2. The README's non-interactive one-skill example names docker-compose-patterns and passes --yes. That line is a different skill and is not the command recorded here.
  3. Claude Code's plugin alternative in the README is `/plugin marketplace add docker/skills` and `/plugin install docker-skills@docker`. This review did not install a plugin.

Before you start

  • Node.js with npx if the skills CLI command is used
  • An agent that can read an Agent Skills directory
  • Standalone sbx with sbx env support, only if an operator later runs a command; this review did not

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-env/SKILL.md

    Supports: Plan versus apply, host-command approval, preRemove removal gates, and the checked-in secret refusal

  2. Repository README ↗Checked

    https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/README.md

    Supports: npx skills add docker/skills and the Apache-2.0 badge

  3. Repository LICENSE ↗Checked

    https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/LICENSE

    Supports: Apache License Version 2.0

  4. https://raw.githubusercontent.com/docker/skills/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-env/SKILL.md

    Supports: upstreamDescription, review.notTested, review.reviewedAt

  5. https://raw.githubusercontent.com/docker/skills/f79172733725e2fd236343ee7b963c446ed85d09/README.md

    Supports: install.command

Evidence & Ask