claudeskills.page

14 skills · 9 categories

Claude Code skills for Docker

Docker skills for small, cache-friendly, non-root images, Compose setups for local development, container security scanning and dev containers that sandbox Claude Code itself.

Install all 14 Browse the list

Start with these

  1. 1

    Dockerfile Optimization

    Smaller images, cached builds, no root, no leaks

    Claude baselines image size and warm-build time, runs a bundled audit script, then restructures the Dockerfile into dependency, build and runtime stages with lockfiles copied before source. It picks a distroless or slim base, moves build secrets into BuildKit mounts, drops root, and reports before-and-after size, build time and CVE counts in a table.

  2. 2

    Docker Compose

    One command to a working local stack

    Claude builds compose.yaml files where the app waits for a healthy database instead of sleeping, migrations run as a one-shot service, ports bind to localhost, and optional tools sit behind profiles. It separates .env interpolation from container env, sets up Compose Watch for hot reload, and validates everything with docker compose config and up --wait.

  3. 3

    Container Security

    Minimal images, non-root pods, scanned on every build

    Claude fixes container risk at the source: it swaps bloated base images for pinned distroless or slim ones, moves build secrets to BuildKit mounts, runs as a numeric non-root user, and applies a restricted securityContext with dropped capabilities and a read-only root filesystem. Trivy and hadolint gate CI, images get signed, and every change is measured against a CVE baseline.

All 14 Docker skills

Grouped by category. Each card opens the full playbook, example prompts and install commands.

Claude Code Mastery 1

No. 005

Devcontainer Sandboxing

Skip prompts only inside a boundary you have tested

Claude matches the isolation to the risk: the built-in Bash sandbox for fewer prompts on a laptop, a dev container with a non-root user, persisted config and a default-deny egress firewall for teams, or a disposable container for unattended bypass runs. Every boundary is proven with escape tests, credentials stay scoped, and bypass mode is used only where the tests passed.

devcontainer-sandboxing 197 lines

Backend & APIs 1

No. 079

Bun Runtime

Adopt Bun one role at a time, with proof

Claude treats Bun as four separate tools and adopts the low-risk ones first: package manager, then test runner, then bundler, then runtime. It commits the text lockfile, freezes it in CI, audits blocked install scripts, writes Bun.serve handlers with graceful shutdown and raised idle timeouts, and proves Node compatibility with the real suite and a staging image before anything ships.

bun-runtime 223 lines

Testing 2

No. 141

Testcontainers

Real databases in tests, started once and reset fast

Claude replaces database mocks and H2 stand-ins with the production engine in a container, started once per run rather than per test. It runs the real migrations, picks rollback, truncation, template databases or snapshots for isolation, gives each parallel worker its own database, and sets up GitHub Actions or GitLab Docker-in-Docker so the suite passes cold, shuffled and in parallel.

testcontainers 202 lines · 2 files
No. 144

Visual Regression

Screenshot tests that fail on real change, not noise

Claude makes renders deterministic before touching thresholds: frozen clock, fixture data, loaded fonts, masked live widgets, and baselines generated inside the same Playwright container CI uses. It proves zero noise with repeated runs, then tunes per-snapshot limits so a one-pixel padding change fails while anti-aliasing jitter does not.

visual-regression 179 lines

DevOps & SRE 4

No. 153

Dockerfile Optimization

Smaller images, cached builds, no root, no leaks

Claude baselines image size and warm-build time, runs a bundled audit script, then restructures the Dockerfile into dependency, build and runtime stages with lockfiles copied before source. It picks a distroless or slim base, moves build secrets into BuildKit mounts, drops root, and reports before-and-after size, build time and CVE counts in a table.

dockerfile-optimization 232 lines · 2 files
No. 152

Docker Compose

One command to a working local stack

Claude builds compose.yaml files where the app waits for a healthy database instead of sleeping, migrations run as a one-shot service, ports bind to localhost, and optional tools sit behind profiles. It separates .env interpolation from container env, sets up Compose Watch for hot reload, and validates everything with docker compose config and up --wait.

docker-compose 226 lines
★ No. 154

GitHub Actions

Faster CI, read-only tokens, zero stored cloud keys

Claude rewrites workflows so irrelevant changes skip CI, superseded runs cancel, and package and Docker caches make the warm path fast. Tokens default to read-only, deploys use OIDC with subject-restricted trust policies and protected environments, and untrusted PR text never reaches a shell. Results are linted with actionlint and zizmor and reported with before-and-after timings.

github-actions 227 lines · 2 files
No. 150

CI Pipeline Speed

Shorten the critical path, prove it with medians

Claude baselines several recent runs with a bundled analyzer that finds the critical path, queue delay and slowest steps, then works on that path only: removing duplicate work, adding correctly keyed caches, sharding tests by timing data, and running affected-only builds in monorepos. Results are reported as before-and-after medians with test counts unchanged.

ci-pipeline-speed 171 lines · 2 files

Cloud Platforms 2

★ No. 191

VPS Deployment

One server, done properly: TLS, backups, no-drop deploys

Claude sets up a VPS the way an experienced operator would: key-only SSH, a firewall that Docker cannot bypass, Compose services on internal networks behind Caddy with automatic TLS, and a deploy script that starts a healthy replica before draining the old one. Nightly restic and pg_dump backups go off-site with a restore test, and exposure is verified from outside the server.

vps-deployment 272 lines · 2 files
No. 175

AWS Lambda

Fast cold starts, safe retries, no silent drops

Claude writes Lambda handlers that create clients once at init, stay well inside timeouts, and return partial batch failures so one bad SQS message does not replay the rest. It measures Init Duration before tuning, chooses between bundling, arm64, SnapStart and provisioned concurrency, and makes sure every async trigger has a failure destination and alarms.

aws-lambda 184 lines · 2 files

Data Engineering 1

No. 234

Streamlit Apps

Data apps that do not re-query on every click

Claude designs Streamlit apps around the rerun model: data loaders cached with TTLs, shared clients in cache_resource, multi-input filters inside forms, and live panels in fragments so one widget does not refresh the world. State lives in session_state with stable keys and callbacks, secrets come from st.secrets, and an AppTest suite covers the main path before deploy.

streamlit-apps 210 lines

Security 1

No. 273

Container Security

Minimal images, non-root pods, scanned on every build

Claude fixes container risk at the source: it swaps bloated base images for pinned distroless or slim ones, moves build secrets to BuildKit mounts, runs as a numeric non-root user, and applies a restricted securityContext with dropped capabilities and a read-only root filesystem. Trivy and hadolint gate CI, images get signed, and every change is measured against a CVE baseline.

container-security 209 lines

Performance 1

No. 299

JVM Tuning

GC logs and JFR first, then a short flag set with reasons

Claude starts by recording the JDK version, collector, heap, container limits and a stated latency goal, then gathers GC logs and a Flight Recorder capture under real load. It classifies the problem, such as humongous allocations, an undersized heap, native memory overrun or CPU throttling, fixes allocation causes before flags, and ends with a short flag set where every entry has a reason.

jvm-tuning 183 lines · 2 files

Automation & Tooling 1

No. 499

n8n Workflows

n8n automations that retry safely and report failures

Claude builds n8n workflows item by item with pinned test data, dedupes webhook deliveries, sets per-node retries and an error workflow that posts the execution link, and keeps secrets in credentials only. It knows the 2.x save-versus-publish model and new defaults, exports workflows to git, and self-hosts with Postgres, external task runners and a backed-up encryption key.

n8n-workflows 191 lines

Install

Every Docker skill in one command

Installs into ~/.claude/skills/. Add --project after -- to install into the current repository.

curl -fsSL https://claudeskills.page/install.sh | sh -s -- dockerfile-optimization docker-compose container-security devcontainer-sandboxing vps-deployment testcontainers n8n-workflows github-actions bun-runtime visual-regression ci-pipeline-speed aws-lambda streamlit-apps jvm-tuning

Docker skills FAQ

What is the best Claude Code skill for Docker?

Start with Dockerfile Optimization: Smaller images, cached builds, no root, no leaks. Then add Docker Compose and Container Security, which cover the next most common Docker requests.

How do I install all 14 Docker skills at once?

Pass every name to the installer in one command: curl -fsSL https://claudeskills.page/install.sh | sh -s -- dockerfile-optimization docker-compose container-security devcontainer-sandboxing vps-deployment testcontainers n8n-workflows github-actions bun-runtime visual-regression ci-pipeline-speed aws-lambda streamlit-apps jvm-tuning. Add --project to install them into the current repository's .claude/skills/ folder so your team gets them too.

Do these Docker skills work outside Claude Code?

Yes. Each skill uses only the portable Agent Skills frontmatter, so the same folder works on claude.ai, through the Claude API and in the Agent SDK. Skills that run bundled scripts need an environment with code execution.

Related technologies

esc