SkillAgentSearch skills...

docker-development

Analyse Dockerfiles and Compose files for security, image size, cache and config problems, with CI-ready exit codes

Install / Use

npx skills add borghei/Claude-Skills --skill docker-development

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Category

Security

Supported Platforms

Universal

Our assessment of docker-development

docker-development scores 88/100 on our quality scale, 631st of 1,096 Security skills we index.

Its SKILL.md is 6.0 KB long, well organised into 25 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
29/30
Structure
20/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so docker-development is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

docker-development compared with similar skills

All 4 of these similar skills score higher than docker-development; compare them before choosing.

SkillScoreStarsUpdatedFormat
docker-development (this skill)by borghei8881757d agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md
LocalAIby mudler10050.4ktodayMCP Server
x402by browser-use100121.0k4d agoSKILL.md

Frequently asked questions

How do I install docker-development?
Run npx skills add borghei/Claude-Skills --skill docker-development. The install tabs above show the steps for each supported agent.
Which AI agents does docker-development work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is docker-development safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is docker-development still maintained?
The repository was last updated about 2 months ago, so docker-development is actively maintained.

name: docker-development description: > This skill should be used when the user asks to "analyze a Dockerfile", "optimize Docker layers", "validate docker-compose", "check container best practices", or "audit Docker configurations". license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: engineering domain: containers updated: 2026-04-02 tags: [docker, containers, devops, compose, dockerfile]

Docker Development

Category: Engineering Domain: Container Development & Optimization

Overview

The Docker Development skill provides automated analysis of Dockerfiles and docker-compose configurations. It identifies layer optimization opportunities, security issues, best practice violations, and compose service misconfigurations. Use this skill to enforce container standards across your team and catch issues before they reach production.

Clarify First

Before running the analysis, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] Target file — which Dockerfile or docker-compose.yml to analyze (sets --file and which tool runs)
  • [ ] Focus — full analysis vs security-only, and whether to check port conflicts (sets --security-only/--check-ports)
  • [ ] Output mode — human-readable vs JSON for CI (sets --format json and whether findings gate a pipeline)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start

# Analyze a Dockerfile for best practices
python scripts/dockerfile_analyzer.py --file Dockerfile

# Analyze with JSON output
python scripts/dockerfile_analyzer.py --file Dockerfile --format json

# Validate a docker-compose file
python scripts/compose_validator.py --file docker-compose.yml

# Check for port conflicts across compose files
python scripts/compose_validator.py --file docker-compose.yml --check-ports

Tools Overview

dockerfile_analyzer.py

Analyzes Dockerfiles for best practices, security issues, and optimization opportunities.

| Feature | Description | |---------|-------------| | Layer optimization | Detects unnecessary layers, recommends combining RUN statements | | Multi-stage analysis | Validates multi-stage build patterns and final image size | | Security scanning | Flags running as root, use of latest tags, exposed secrets | | Base image checks | Recommends smaller base images (alpine, distroless, slim) | | Cache optimization | Identifies poor layer ordering that breaks Docker cache |

# Full analysis
python scripts/dockerfile_analyzer.py --file Dockerfile

# Security-focused scan
python scripts/dockerfile_analyzer.py --file Dockerfile --security-only

# JSON output for CI integration
python scripts/dockerfile_analyzer.py --file Dockerfile --format json

compose_validator.py

Validates docker-compose files for correctness, dependency issues, and port conflicts.

| Feature | Description | |---------|-------------| | Schema validation | Checks compose file structure and syntax | | Dependency graph | Validates depends_on chains for circular dependencies | | Port conflict detection | Identifies duplicate host port bindings | | Volume mount checks | Validates volume paths and mount configurations | | Network analysis | Checks network definitions and service connectivity |

# Full validation
python scripts/compose_validator.py --file docker-compose.yml

# Check port conflicts only
python scripts/compose_validator.py --file docker-compose.yml --check-ports

# JSON output
python scripts/compose_validator.py --file docker-compose.yml --format json

Workflows

Dockerfile Review Workflow

  1. Analyze - Run dockerfile_analyzer.py against the target Dockerfile
  2. Review findings - Address critical security issues first (root user, secrets)
  3. Optimize layers - Combine RUN statements, reorder for cache efficiency
  4. Validate base images - Switch to minimal base images where possible
  5. Re-analyze - Confirm improvements and verify no regressions

Compose Validation Workflow

  1. Validate structure - Run compose_validator.py for syntax and schema checks
  2. Check dependencies - Review service dependency graph for circular refs
  3. Audit ports - Ensure no host port conflicts across services
  4. Review volumes - Confirm volume mounts are correct and necessary
  5. Network review - Verify service isolation and connectivity

CI Integration Workflow

# Example GitHub Actions step
- name: Docker Lint
  run: |
    python scripts/dockerfile_analyzer.py --file Dockerfile --format json > results.json
    python scripts/compose_validator.py --file docker-compose.yml --format json >> results.json

Reference Documentation

Common Patterns Quick Reference

| Pattern | Good | Bad | |---------|------|-----| | Base image | FROM python:3.12-slim | FROM python:latest | | User | USER appuser | Running as root | | Layer combining | RUN apt-get update && apt-get install -y pkg | Separate RUN for update and install | | COPY ordering | Copy requirements first, then code | Copy everything at once | | Multi-stage | Use builder stage + minimal runtime | Single stage with build tools | | Secrets | Use build secrets or env at runtime | COPY .env . or ENV SECRET=value | | Health checks | HEALTHCHECK CMD curl -f http://localhost/ | No health check defined | | .dockerignore | Include node_modules, .git, etc. | No .dockerignore file |

Compose Patterns

| Pattern | Good | Bad | |---------|------|-----| | Restart policy | restart: unless-stopped | No restart policy | | Resource limits | deploy.resources.limits set | Unlimited resources | | Named volumes | volumes: [db-data:/var/lib/postgresql] | Anonymous volumes | | Networks | Explicit network definitions | Default bridge only | | Environment | env_file: .env | Inline secrets in compose |

Related Skills

View on GitHub
GitHub Stars817
CategorySecurity
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium
docker-development — Universal Skill: Install & Safety Check | SkillAgent