generating-docker-compose-files

This skill enables Claude to generate Docker Compose configurations for multi-container applications. It leverages best practices for production-ready deployments, including defining services, networks, volumes, health checks, and resource limits. Claude should use this skill when the user requests a Docker Compose file, specifies application architecture involving multiple containers, or mentions needs for container orchestration, environment variables, or persistent data management in a Docker environment. Trigger terms include "docker-compose", "docker compose file", "multi-container", "container orchestration", "docker environment", "service definition", "volume management", "network configuration", "health checks", "resource limits", and ".env files".

1.03x

Quality

53%

Does it follow best practices?

Impact

98%

1.03x

Average score across 9 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/devops/docker-compose-generator/skills/docker-compose-generator/SKILL.md

Evaluation results

100%

10%

Container Orchestration for an E-Commerce Platform

Service dependencies and environment config

Criteria

Without context

With context

File named docker-compose.yml

100%

depends_on directive used

100%

.env file referenced

100%

.env file created

100%

Named volumes used

100%

No host-path bind mounts for data

100%

Network defined

100%

Services section complete

100%

Volumes section complete

100%

Production-Ready Compose Setup for a Job Queue System

Health checks and resource limits

Criteria

Without context

With context

File named docker-compose.yml

100%

Health check on cache service

100%

Health check on database service

100%

Resource limits defined

100%

Memory limit present

100%

Named volumes used

100%

depends_on directive used

100%

Healthcheck interval/timeout set

100%

Restart policy set

100%

90%

Containerized SaaS Platform with Isolated Service Tiers

Network isolation and environment secrets

Criteria

Without context

With context

File named docker-compose.yml

100%

Multiple networks defined

100%

Network isolation enforced

100%

.env file referenced

100%

.env file written

100%

Named volumes used

100%

Resource limits applied

depends_on used

100%

No hardcoded passwords

100%

Top-level volumes section present

100%

Video Processing Pipeline Infrastructure

Message queue worker resilience

Criteria

Without context

With context

File named docker-compose.yml

100%

Broker health check present

100%

Worker depends_on broker

100%

Resource limits on workers

100%

Memory limit specified

100%

Restart policy set

100%

.env file referenced

100%

.env file written

100%

Named volumes used

100%

Top-level volumes section

100%

Healthcheck interval/timeout

100%

10%

Containerized Observability Platform

Monitoring stack network isolation

Criteria

Without context

With context

File named docker-compose.yml

100%

Multiple networks defined

100%

Monitoring network isolation

100%

Named volumes for metrics data

100%

Named volumes for Grafana data

100%

Top-level volumes section

100%

.env file referenced

100%

.env file written

100%

No hardcoded passwords

100%

Health check on metrics collector

100%

Grafana depends_on Prometheus

100%

E-Commerce Microservices Local Environment

API gateway microservices composition

Criteria

Without context

With context

File named docker-compose.yml

100%

Gateway depends_on backends

100%

Backend service health checks

100%

Healthcheck interval/timeout set

100%

Internal vs public networks

100%

Database not on public network

100%

Resource limits applied

100%

Named volumes for stateful services

100%

Top-level volumes key present

100%

.env file referenced

100%

.env file written

100%

Restart policy set

100%

11%

Internal Developer Platform Setup

Self-hosted development tooling volumes and secrets

Criteria

Without context

With context

File named docker-compose.yml

100%

Named volumes for Gitea data

100%

Named volumes for Drone/CI state

100%

Named volumes for registry data

100%

Top-level volumes section present

100%

.env file referenced

100%

.env file written

100%

No hardcoded passwords

100%

depends_on used

100%

Custom network defined

100%

Health check on Gitea

100%

Centralized Log Aggregation Platform

Log aggregation stack resource limits and health checks

Criteria

Without context

With context

File named docker-compose.yml

100%

Resource limits on search engine

100%

Resource limits on at least two services

100%

Health check on search engine

100%

Healthcheck interval and timeout set

100%

Dashboard depends_on search engine

100%

Named volumes for index data

100%

Top-level volumes section

100%

Multiple networks defined

100%

.env file referenced

100%

.env file written

100%

ML Experiment Tracking Platform

ML experiment tracking storage and credentials

Criteria

Without context

With context

File named docker-compose.yml

100%

.env file referenced

100%

.env file written

100%

No hardcoded credentials

100%

Named volume for database

100%

Named volume for artifact store

100%

Top-level volumes section

100%

Restart policy set

100%

MLflow depends_on database

100%

MLflow depends_on object store

100%

Health check on database or object store

100%

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 13d35b8

Evaluated: about 2 months ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Container Orchestration for an E-Commerce Platform Production-Ready Compose Setup for a Job Queue System Containerized SaaS Platform with Isolated Service Tiers Video Processing Pipeline Infrastructure Containerized Observability Platform E-Commerce Microservices Local Environment Internal Developer Platform Setup Centralized Log Aggregation Platform ML Experiment Tracking Platform

Is this your skill?

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.