docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

78%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.

The content is highly actionable with complete executable examples and a well-sequenced, validated harness workflow. It loses points on progressive disclosure because everything is inlined into one long file with no real reference bundles, despite referencing external paths that do not exist.

Suggestions

Move the long ECC CLI installer harness section into a dedicated reference file (e.g. references/installer-harness.md) and keep a concise summary plus a one-level-deep link in SKILL.md.

Either provide the referenced bundle files (docker/plugin-setup/compose.yaml, docker/plugin-setup/interactive-plan.js) or rephrase the in-body references so they do not imply files that are absent from the bundle.

Tighten a few self-evident inline comments (e.g. '# Bind mount for hot reload') to lift conciseness toward fully lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean: code blocks with terse inline comments and minimal prose, assuming Claude's competence without explaining Docker basics. A few comments and the long ECC harness section are slightly heavier than strictly needed, keeping it just below fully efficient.	4 / 5
Actionability	Provides complete, copy-paste-ready artifacts (full docker-compose.yml, multi-stage Dockerfile, exact docker compose commands) covering the common cases with concrete executable guidance throughout.	5 / 5
Workflow Clarity	The ECC harness section is an explicit sequenced workflow with validation checkpoints ('docker compose config --quiet' to validate the model before building, inspect image identity before trusting), but the reference-style sections (Compose, Networking, Volumes) lack sequencing, so minor gaps remain.	4 / 5
Progressive Disclosure	The body is well-organized by section headers but is a single ~515-line monolith with all content inlined; no bundle files exist, yet referenced paths like 'docker/plugin-setup/compose.yaml' and 'docker/plugin-setup/interactive-plan.js' have no corresponding bundle files, and the large ECC harness section could be split into a separate reference.	3 / 5
	Total	16 / 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.

The description is specific, complete, and distinctive, with concrete capability areas and an explicit 'Use when' clause covering several natural trigger scenarios. Trigger term coverage is strong though not exhaustive of every synonym or file extension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas ('hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration') and specific actions ('creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions'), giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both 'what' (the pattern domains it covers) and 'when' ('Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keywords ('Dockerfiles and Compose services', 'installers across Linux distributions', 'macOS and Windows validation'), but a few natural variants/file extensions are absent, so it sits just below fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	A clear niche combining Docker dev patterns with CLI installer-harness testing and platform-boundary language yields distinct triggers with minimal conflict risk against other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (521 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/docker-patterns/SKILL.md
Commit: e04ea0b

Reviewed: 2 days 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.