菜单
Recover Docker inside Mighty sandboxes when tasks use `docker`, `docker compose`, Testcontainers, or the local dev stack. Starts DinD on demand, re-checks readiness, and surfaces dockerd diagnostics instead of assuming Docker stayed up after resume.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sandbox-docker |
| description | Recover Docker inside Mighty sandboxes when tasks use `docker`, `docker compose`, Testcontainers, or the local dev stack. Starts DinD on demand, re-checks readiness, and surfaces dockerd diagnostics instead of assuming Docker stayed up after resume. |
docker, docker compose, Testcontainers, or sandbox local-stack commands.docker info fails in a resumed or long-lived sandbox.dockerd diagnostics before debugging app-level failures.bash scripts/ensure-docker.sh
bash scripts/docker-doctor.sh
ensure-docker.sh succeeds should you run docker compose, Testcontainers, image builds, or local-stack commands.ensure-docker.sh treats mighty-dind-preflight or sandbox-dind-preflight.sh as the source of truth for daemon startup.docker-doctor.sh surfaces the active dockerd processes, socket and pidfile state, relevant MIGHTY_DIND_* env vars, and the recent dockerd log from ${MIGHTY_DIND_DOCKERD_LOG:-/tmp/mighty-dockerd.log}.Upload local screenshot/video artifacts from agent runs and return renderable file embeds (`![[file ...]]`) plus `mighty-file:` refs for thread UI previews.
Use when the user uploads files or a .zip archive (like user research or logs). Describes how to locate attached files in the sandbox, extract archives if necessary, synthesize findings, and save results back to Mighty.
Record durable architectural or policy choices with `mt decision`. Use when choosing between alternatives, setting lasting constraints, superseding an accepted decision, or capturing significant rationale while context is fresh.
Use when a workstream needs a reviewable deliverable, especially a GitHub PR. Covers `mt pr` for the normal PR-backed path, `mt artifact create` for existing deliverables, and the workstream delivery contract that hands PRs into review and merge gates.
Use when asked to write, migrate, or organize long-form Mighty docs, or decide whether something should be a doc or a spec/task/decision. Covers `mt doc` authoring, doc types, and when guides or runbooks should live in the Mighty graph instead of standalone repo markdown.
Use Mighty-native eval primitives from external repos. Covers the native eval record model, local or hosted write-back flows, and when to reach for the deeper `external-evals` skill for framework-specific mapping.