Agent skill · software engineering · rknall
Docker Configuration Validator
Comprehensive Docker and Docker Compose validation following best practices and security standards. Use this skill when users ask to validate Dockerfiles, review Docker configurations, check Docker Compose files, verify multi-stage builds, audit Docker security, or ensure compliance with Docker best practices. Validates syntax, security, multi-stage builds, and modern Docker Compose requirements.
Why this skill is useful
Adds validation scripts and specific commands for Dockerfile and Docker Compose compliance that the AI wouldn't reliably generate on its own.
What it needs
Requires dclint, docker, hadolint installed locally. About 11k tokens when loaded. Last updated 2025-10-20. 58 stars on the source repository.
What this skill does
Docker Configuration Validator This skill provides comprehensive validation for Dockerfiles and Docker Compose files, ensuring compliance with best practices, security standards, and modern syntax requirements. When to Use This Skill Activate this skill when the user requests: Validate Dockerfiles or Docker Compose files Review Docker configurations for best practices Check for Docker security issues Verify multi-stage build implementation Audit Docker setup for production readiness Ensure modern Docker Compose syntax compliance Fix Docker configuration issues Create validation scripts or CI/CD integration Core Workflow Phase 1: Initial Assessment When a user requests Docker validation, start by understanding the scope: 1. Identify What to Validate Single Dockerfile or multiple? Docker Compose file(s)? Entire project directory? Specific concerns or focus areas? Production vs development environment? 2. Understand Requirements Security compliance level needed? Multi-stage build requirement? Performance constraints? CI/CD integration needed? Automated validation script desired? 3. Check Available Tools Is Hadolint available? (Dockerfile linter) Is DCLint available? (Docker Compose linter) Is Docker CLI available? Should tools be installed as part of process? Phase 2: Dockerfile Validation Step 1: Locate Dockerfiles Find all Dockerfiles in the project: Step 2: Run Hadolint Validation If Hadolint is available: If Hadolint is NOT available: Perform manual validation using built-in checks (see Step 3) Recommend Hadolint installation Provide installation instructions Step 3: Manual Dockerfile Validation Check each Dockerfile for critical issues: 1. Base Image Best Practices ✅ Check: No :latest tags ✅ Check: Specific version pinned ✅ Check: Uses minimal base images (alpine/slim variants) ✅ Check: Trusted registry used 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rknall/docker-validation