docker-development

Docker and container development agent skill and plugin for Dockerfile optimization, docker-compose orchestration, multi-stage builds, and container security hardening. Use when: user wants to optimize a Dockerfile, create or improve docker-compose configurations, implement multi-stage builds, audit container security, reduce image size, or follow container best practices. Covers build performance, layer caching, secret management, and production-ready container patterns.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable content with executable examples and clear workflows, undermined by duplicated inline material that already lives in unlinked reference files. Tightening the body to point at the references would improve both conciseness and progressive disclosure.

Suggestions

Replace the inlined optimization/compose/security checklists with pointers to references/compose-patterns.md and references/dockerfile-best-practices.md to remove duplication and shrink the body.

Add explicit validate->fix->retry feedback loops to the /docker:compose and /docker:security workflows, and specify what to do when the optimize validation step fails.

Either provide scripts/convert.sh or remove the multi-tool install command that references it, so cited bundle paths all resolve.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and opinionated, but the body inlines large ASCII checklists and three full Dockerfile patterns that duplicate material already present in the reference files, adding tokens Claude largely already knows.	3 / 5
Actionability	Fully executable guidance — complete Go/Node/Python multi-stage Dockerfiles, concrete analyzer/validator CLI invocations, and severity-to-fix tables that are copy-paste ready across common cases.	5 / 5
Workflow Clarity	Three numbered workflows with an explicit 'Validate' step in the optimize flow, but the compose and security workflows lack explicit validate->fix->retry feedback loops and the optimize validation does not specify failure handling.	4 / 5
Progressive Disclosure	Bundle reference files (compose-patterns.md, dockerfile-best-practices.md) exist but are never linked from the body, while their content is duplicated inline; the referenced convert.sh is not present in the bundle.	3 / 5
	Total	15 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states capabilities and provides explicit 'Use when' trigger guidance with concrete scenarios. Minor room to add a few synonyms and file-extension terms for trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'Dockerfile optimization, docker-compose orchestration, multi-stage builds, and container security hardening' plus 'optimize a Dockerfile...reduce image size' — giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both 'what' (optimization, orchestration, multi-stage, security hardening) and 'when' with a concrete 'Use when:' clause enumerating trigger scenarios.	5 / 5
Trigger Term Quality	Strong natural phrases users would say ('optimize a Dockerfile', 'docker-compose', 'reduce image size', 'audit container security') but missing a few synonyms and file extensions like '.dockerignore' or 'build cache' as standalone terms.	4 / 5
Distinctiveness Conflict Risk	A clear container/Docker niche with distinct triggers (Dockerfile, docker-compose, image size) and minimal overlap with adjacent DevOps or security skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: engineering/docker-development/skills/docker-development/SKILL.md
Commit: 19392f7

Reviewed: ~7 hours ago

Table of Contents

Discovery Implementation Validation

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.