agentsclimarketplace
Sign in

Container review

Skill shinzoxD/knackbox/skills/coding/container-review

Review Dockerfiles and container configs for size, security, and operability. Use whenever the user shares a Dockerfile, compose file, Kubernetes image config, or asks how to harden, slim, or debug a container build.From its SKILL.md

Install
npx -y skills add shinzoxD/knackbox --skill container-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, 287 tokens by cl100k_base, as published. Nobody here has run it

Container Review

Images should be minimal, reproducible, and runnable as non-root with clear health signals.

Checklist

  • Base image: pinned digest/tag policy; avoid latest in prod.
  • Multi-stage builds; no build tooling in final image when possible.
  • Non-root user; read-only root FS when feasible.
  • No secrets in layers (ENV passwords, copied .env).
  • Minimal attack surface: no unused shells/packages if practical.
  • Healthcheck / graceful shutdown notes for orchestrators.
  • Compose: resource limits, networks, bind-mount safety.

Output format

## Container review

### Findings
1. [blocking|important|nit] …

### Recommended Dockerfile sketch
…

### Build/run verify
…

Rules

  1. Prefer distroless/slim only when debugging trade-offs are accepted.
  2. Pin versions; explain rebuild policy.
  3. Never suggest baking prod secrets into images.
  4. Order layers for cache efficiency after correctness/security.
  5. Call out root containers in K8s as important when relevant.
  6. Do not invent base image CVEs; speak in classes of risk if versions unknown.

Edge cases

  • GPU / exotic bases: document host deps.
  • Windows containers: separate guidance; do not assume Linux paths.
  • Supply chain: SBOM/signing as optional hardening.

What ships with it: 1 file

1.2 KB alongside SKILL.md

benchmarks/

Keep looking

Skills are one crate of 326,782. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.