Docker and Kubernetes patterns. Triggers on: Dockerfile, docker-compose, kubernetes, k8s, helm, pod, deployment, service, ingress, container, image.
84
Quality
75%
Does it follow best practices?
Impact
100%
1.25xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/container-orchestration/SKILL.mdDockerfile best practices
Specific base image version
100%
100%
Multi-stage build
0%
100%
Dependency-first copy
100%
100%
No dev dependencies in production
100%
100%
Non-root user created
100%
100%
Non-root user active
100%
100%
WORKDIR set
100%
100%
HEALTHCHECK present
0%
100%
PYTHONUNBUFFERED set
100%
100%
.dockerignore excludes noise
0%
100%
No secrets in Dockerfile
100%
100%
Correct CMD/ENTRYPOINT
100%
100%
Without context: $0.1327 · 2m 55s · 12 turns · 15 in / 2,148 out tokens
With context: $0.2344 · 2m 57s · 15 turns · 452 in / 2,310 out tokens
Docker Compose service dependencies
depends_on with condition
100%
100%
db healthcheck defined
100%
100%
web healthcheck defined
0%
100%
Named volume for DB
100%
100%
Pinned postgres image version
100%
100%
db healthcheck uses pg_isready
100%
100%
No secrets hardcoded in image
100%
100%
Services on same network
100%
100%
DATABASE_URL env var
100%
100%
Without context: $0.1903 · 3m 16s · 13 turns · 20 in / 2,474 out tokens
With context: $0.3806 · 3m 46s · 22 turns · 27 in / 3,501 out tokens
Kubernetes manifest authoring
Resource requests defined
100%
100%
Resource limits defined
100%
100%
Liveness probe present
100%
100%
Readiness probe present
100%
100%
Probe delays configured
100%
100%
Secret via secretKeyRef
100%
100%
No hardcoded credentials
100%
100%
ClusterIP service type
100%
100%
Nginx ingress class
0%
100%
Nginx rewrite annotation
0%
100%
Specific image tag
100%
100%
Without context: $0.3653 · 4m 13s · 22 turns · 29 in / 4,663 out tokens
With context: $0.4019 · 4m 13s · 24 turns · 276 in / 4,413 out tokens
5342bca
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.