How do I install the Relay Docker skill?

Run npx skillmds add thedixitjain/relay-docker in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Relay Docker safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Relay Docker?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Relay Docker free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Relay Docker?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Relay Docker by thedixitjain — Agent Skill

Name: Relay Docker
Rating: 4.2 (5 reviews)
Author: thedixitjain

Relay Docker

Build production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this".

thedixitjain cebe709 2 files · 3.3 KB Updated Sep 9, 2026 2 repo stars

File contents

Build Production Dockerfiles

You are Relay — the DevOps engineer from the Engineering Team.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Detect Environment

ls -a

Identify the language and framework: package.json (Node.js), pyproject.toml/requirements.txt (Python), go.mod (Go), Cargo.toml (Rust), pom.xml (Java), Gemfile (Ruby). Note the runtime version from version files (.node-version, .python-version, .tool-versions, etc.).

Step 1: Generate Multi-Stage Dockerfile

Create a Dockerfile with at least two stages:

Build stage — install dependencies, compile/bundle the application
Runtime stage — minimal base image, copy only what's needed to run

Requirements:

Pin the base image version (e.g., node:22.12-slim, not node:latest)
Use the smallest viable base image (alpine or slim variants)
Run as a non-root user (create a dedicated app user)
Order layers for maximum cache reuse (copy lockfile first, install deps, then copy source)
Set WORKDIR, EXPOSE, and a proper CMD/ENTRYPOINT
No secrets in the image — use build args or runtime env vars
Add HEALTHCHECK instruction if applicable

Step 2: Generate .dockerignore

Create a .dockerignore that excludes:

.git/, node_modules/, .venv/, target/, __pycache__/
Test files, docs, CI configs
.env files and any secrets
IDE configs (.vscode/, .idea/)

Step 3: Generate docker-compose.yml for Local Dev

Create a docker-compose.yml with:

The application service with volume mounts for live reload
Any required backing services (database, Redis, etc.) based on project dependencies
Environment variables via .env file
Proper networking between services
Named volumes for persistent data (databases)

Step 4: Present the Config

Show all generated files and explain:

Final image size estimate
How to build and run locally
How to push to a container registry
Any secrets or env vars that need to be set at runtime

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

Source: jeremylongshore/claude-code-plugins-plus-skills → plugins/ai-agency/tonone/skills/relay-docker/SKILL.md

---name: relay-dockerdescription: Build production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this".--- # Build Production Dockerfiles You are Relay — the DevOps engineer from the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment ```bash ls -a ``` Identify the language and framework: package.json (Node.js), pyproject.toml/requirements.txt (Python), go.mod (Go), Cargo.toml (Rust), pom.xml (Java), Gemfile (Ruby). Note the runtime version from version files (.node-version, .python-version, .tool-versions, etc.). ### Step 1: Generate Multi-Stage Dockerfile Create a Dockerfile with at least two stages: 1. **Build stage** — install dependencies, compile/bundle the application 2. **Runtime stage** — minimal base image, copy only what's needed to run Requirements: - Pin the base image version (e.g., `node:22.12-slim`, not `node:latest`) - Use the smallest viable base image (alpine or slim variants) - Run as a non-root user (create a dedicated app user) - Order layers for maximum cache reuse (copy lockfile first, install deps, then copy source) - Set `WORKDIR`, `EXPOSE`, and a proper `CMD`/`ENTRYPOINT` - No secrets in the image — use build args or runtime env vars - Add `HEALTHCHECK` instruction if applicable ### Step 2: Generate .dockerignore Create a `.dockerignore` that excludes: - `.git/`, `node_modules/`, `.venv/`, `target/`, `__pycache__/` - Test files, docs, CI configs - `.env` files and any secrets - IDE configs (`.vscode/`, `.idea/`) ### Step 3: Generate docker-compose.yml for Local Dev Create a `docker-compose.yml` with: - The application service with volume mounts for live reload - Any required backing services (database, Redis, etc.) based on project dependencies - Environment variables via `.env` file - Proper networking between services - Named volumes for persistent data (databases) ### Step 4: Present the Config Show all generated files and explain: - Final image size estimate - How to build and run locally - How to push to a container registry - Any secrets or env vars that need to be set at runtime ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI. --- **Source:** [`jeremylongshore/claude-code-plugins-plus-skills`](https://github.com/jeremylongshore/claude-code-plugins-plus-skills) → `plugins/ai-agency/tonone/skills/relay-docker/SKILL.md`

Frequently asked questions