docker-validator

Validate Docker environments and container health for Stage 5 compliance.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ribatshepo/Auto-Orchestrate --skill docker-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-validator
Source: https://github.com/ribatshepo/Auto-Orchestrate/tree/main/claude-code/skills/docker-validator
Command: npx skills add https://github.com/ribatshepo/Auto-Orchestrate --skill docker-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Docker environment validation and end-to-end readiness checks are automated to ensure Stage 5 compliance, capturing a stable baseline for later restoration.

Core Features & Use Cases

  • Validate Docker Engine, Compose availability, and healthcheck coverage across all services.
  • Capture a pre-test state and restore it after tests to prevent state bleed between runs.
  • Build, deploy, test endpoints (unauthenticated and authenticated when credentials provided), and generate a comprehensive report.

Quick Start

Run the docker-validator skill in a local environment with a running Docker daemon and a valid docker-compose.yml path.

Frequently Asked Questions about docker-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Docker container health checks before deploying to production?

You can validate Docker container health checks by verifying healthcheck coverage across all services and testing endpoint responses. This ensures your containers meet Stage 5 compliance requirements before finalization, capturing a stable baseline for later restoration if needed.

How do I prevent state bleed between Docker Compose test runs?

To prevent state bleed between Docker Compose test runs, capture a pre-test baseline state and restore it after tests complete. This deterministic state capture and restoration approach preserves your environment configuration across multiple CI deployment cycles.

Does Docker environment validation work for both local and CI deployments?

Docker environment validation works for both local and CI deployments by verifying the Docker Engine, Compose availability, and endpoint responses. It requires a running Docker daemon and a valid docker-compose.yml path to execute properly.

Can I test authenticated Docker endpoints during container validation?

You can test authenticated Docker endpoints during container validation by providing credentials to the validation process. It tests both unauthenticated and authenticated endpoint responses, ensuring secure zero-log credential handling while generating a comprehensive summary report.

What is included in a Docker validation summary report?

A Docker validation summary report includes verification results for the Docker Engine, Compose availability, healthcheck coverage, and endpoint responses. It also contains an explicit checkpoint file capturing the pre-test baseline state for restoration purposes.

Why do I need to capture a pre-test baseline before running Docker endpoint tests?

Capturing a pre-test baseline before running Docker endpoint tests allows you to restore the original environment state afterward. This prevents configuration drift and state bleed between test runs, satisfying deterministic state capture requirements for reliable deployments.