docker-patterns

Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/docker-patterns/SKILL.md

Quality

Content

65%

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

The skill is highly actionable with complete, executable Docker/Compose examples and good organization, but it is a monolithic file with no progressive disclosure and re-explains some Docker basics Claude already knows, with limited validation checkpoints around destructive commands.

Suggestions

Move detailed security and debugging reference material into separate files (e.g. SECURITY.md, DEBUGGING.md) and link to them from SKILL.md to improve progressive disclosure.

Add explicit validate/confirm checkpoints before destructive commands (e.g. warn and prompt before 'docker compose down -v').

Trim prose that restates Docker fundamentals Claude already knows, keeping only non-obvious patterns and decisions.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with well-commented code, but inline prose restates Docker basics Claude already knows (e.g. 'Containers are ephemeral -- all data lost on restart without volumes') and some sections re-explain rather than just instruct.	2 / 3
Actionability	Provides complete, executable docker-compose.yml, multi-stage Dockerfile, networking, and security snippets that are copy-paste ready with concrete values and commands.	3 / 3
Workflow Clarity	Topics are clearly organized by scenario, but destructive operations like 'docker compose down -v' and image rebuilds lack explicit validation/checkpoint sequencing, and there are no validate-then-proceed feedback loops.	2 / 3
Progressive Disclosure	Content is a single ~358-line monolithic SKILL.md with no bundle files or one-level-deep references; well-sectioned but content that could be split (e.g. security, debugging) is inline rather than offloaded.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 and distinct, naming concrete Docker capability domains, but it omits an explicit 'Use when...' trigger clause and could include more natural user phrasings like 'dockerize' or 'Dockerfile'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up Docker Compose, writing Dockerfiles, or troubleshooting containerized local dev.'

Include natural user terms such as 'dockerize', 'containerize', and 'Dockerfile' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas: 'local development, container security, networking, volume strategies, and multi-service orchestration' — several specific actions/domains rather than vague language.	3 / 3
Completeness	Clearly answers 'what' (the capability domains) but has no explicit 'Use when...' trigger clause — 'when' is only implied, which caps completeness at 2 per the guideline.	2 / 3
Trigger Term Quality	Contains relevant natural terms ('Docker', 'Docker Compose', 'containers') but lacks common phrasings a user would say such as 'dockerize', 'containerize', or 'Dockerfile'; missing some common variations.	2 / 3
Distinctiveness Conflict Risk	Clearly a Docker-specific niche with distinct triggers (Docker Compose, container security, multi-service orchestration) unlikely to conflict with unrelated skills.	3 / 3
	Total	10 / 12 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/docker-patterns/SKILL.md
Commit: 0c1d7be

Reviewed: about 10 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.