Harden a Docker build before release with explicit runtime contracts, secret controls, supply-chain evidence, verification gates, and rollback.
A smaller image is not automatically a safer image. Alpine can break native dependencies. Distroless can remove a shell your health check expects. A precise base tag can still move, and deleting a credential in a later layer does not remove it from image history.
This skill reviews the whole release boundary: build context, dependency lock, stages, copied artifacts, BuildKit secrets, runtime user, writable paths, process signals, target platforms, SBOM, provenance, signatures, scans, promotion, and rollback. It separates observed evidence from assumptions and proposed commands, then returns a release verdict controlled by the missing or failed gates.
Use it for a new Dockerfile, a change review, a release check, or an image incident. The package does not build, push, sign, or deploy by default. It does not invent CVEs, digests, image sizes, cache wins, scanner output, or compatibility proof.
Input
Review this Node Dockerfile. It accepts NPM_TOKEN as an ARG, writes it to .npmrc, copies the repository, deletes .npmrc later, and runs as root on node:22-alpine. We ship amd64 and arm64 to Kubernetes with a read-only root filesystem.
Output
A do-not-release verdict, credential containment and rotation steps, a clean no-cache rebuild with BuildKit secret delivery, a glibc-versus-musl compatibility gate, non-root ownership and writable-path corrections, platform-specific smoke tests, and promotion of a newly verified digest.
Input
Harden this Python 3.12 API image. The team wants Alpine or distroless because the current slim image is 410 MB. The service uses a native wheel, CA certificates, Europe/Warsaw timezone data, a writable model cache, and a curl-based health check.
Provide the Dockerfile and the build, CI, runtime, and deployment evidence you have. Include the application stack, lockfiles, target platforms, entrypoint, required writable paths, secret delivery, scanner or attestation output, and rollout constraints when available. Ask for a new build design, change review, release verdict, or incident repair. The skill returns an image contract, evidence-bound findings, a patch plan, verification matrix, and an immutable rollout and rollback plan.
The Dockerfile, build context or repository layout, .dockerignore, package-manager lockfiles, build command, and expected runtime artifacts. Missing files can remain explicit.
Target platforms, entrypoint, ports, health behavior, shutdown budget, native dependencies, certificates, timezone or locale needs, runtime user, and writable paths when known.
CI, registry, deployment, scanner, SBOM, provenance, signature, policy, rollout, and rollback evidence. The skill can design missing checks but will not claim they passed.
SKILL.md; Docker image hardening and release rubric; Agent Skills interface metadata
No reviews yet.
Output
An evidence map and base-image decision that keeps size unverified until measured, checks wheel and libc compatibility, preserves certificates and timezone behavior, redesigns health checking for the chosen runtime, maps non-root ownership and writable paths, and defines build and runtime acceptance checks.
Input
Decide whether this Go image can ship. CI built amd64 and arm64, but only amd64 ran smoke tests. The SBOM names one digest, the scan names another, the signature covers the stable tag, and deployment also references stable. The previous production digest is known.
Output
A do-not-release verdict, an inventory of digest mismatches and missing arm64 evidence, required SBOM, provenance, scan, signature, and smoke-test bindings for the same manifest digest, plus a staged rollout with stop conditions and rollback to the known prior digest.
Creator
Ttorvex
