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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

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

A highly actionable, code-dense reference whose examples are immediately executable and free of padding. Its weaknesses are structural: no sequenced workflow with validation checkpoints (a cap given the destructive cleanup commands it documents) and no progressive disclosure — everything is inlined in one long file with duplicated activation sections.

Suggestions

Add a brief sequenced workflow for the primary use case (e.g., write multi-stage Dockerfile → write compose file → 'docker compose up' → verify with 'docker compose ps' and healthcheck status), including a validate-before-destructive checkpoint for commands like 'docker compose down -v' and 'docker system prune'.

Split stable reference material (the debugging command catalog and container security guide) into references/ files linked from SKILL.md, keeping the compose/Dockerfile patterns and activation triggers inline.

Remove the duplicate 'When to Use This Skill' section (or the 'When to Activate' section) and fold the comment-only Volume Strategies block into the 'Common Patterns' example to eliminate redundancy.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy with terse, load-bearing comments and no explanation of concepts Claude already knows, matching the 'efficient; minor instances of over-explanation' anchor. Not 5 because the near-duplicate 'When to Activate' and 'When to Use This Skill' lists, plus the redundant comment-only Volume Strategies block, could be trimmed.	4 / 5
Actionability	Everything is fully executable and copy-paste ready: a complete docker-compose.yml with healthchecks, a working multi-stage Dockerfile, override files with exact CLI invocations, and a full debugging command reference. This matches the top anchor of 'copy-paste ready code covering the common cases'.	5 / 5
Workflow Clarity	The content is a topic-organized pattern reference with no sequenced workflow (no 'Dockerfile → compose → up → verify' ordering) and no validation/feedback checkpoints; destructive commands like 'docker compose down -v' and 'docker system prune' are flagged but lack a verify-first loop, capping this dimension at 3. Not 2 because per-task guidance within each section is coherent and unambiguous.	3 / 5
Progressive Disclosure	There are no bundle files and all 365 lines live in SKILL.md with good section headers, but self-contained topics like the debugging command reference and container security guide could be split into references. This sits between anchor 3 ('content that should be separate is inline') and anchor 4 ('good structure'), and the under-50-line simple-skill exception does not apply at this length.	3 / 5
	Total	15 / 20 Passed

Description

78%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 description that explicitly covers both what the skill does and when to use it, in third person, with distinct Docker-specific triggers. The main gaps are the generic trigger phrasing and the omission of the most common user terms (Dockerfile, docker-compose.yml), which keep it just below the top anchors.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete coverage areas ("container security, networking, volume strategies, and multi-service orchestration"), which matches the 'several specific actions; minor gaps' anchor. It falls short of 5 because these are topic nouns rather than concrete actions, unlike 'fill forms, merge documents' in the top anchor.	4 / 5
Completeness	Both 'what' ("Docker and Docker Compose patterns for...") and 'when' ("Use when setting up containerized development environments or reviewing Docker configurations") are explicitly present, satisfying the anchor-4 example. Not 5 because the trigger clause is generic compared to the anchor-5 example's concrete phrases (no mention of Dockerfiles, compose files, or debugging).	4 / 5
Trigger Term Quality	It includes good natural keywords users would say — "Docker and Docker Compose", "setting up containerized development environments", "reviewing Docker configurations" — matching the 'good keyword coverage; a few natural terms missing' anchor. Not 5 because very common user terms like "Dockerfile" and "docker-compose.yml" are absent.	4 / 5
Distinctiveness Conflict Risk	The description carves out a clear niche (Docker/Compose patterns for local development) with distinct triggers and minimal overlap risk with other skills, matching the top anchor. Third-person voice is used correctly, so no specificity penalty applies.	5 / 5
	Total	17 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

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

Reviewed: 1 day 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.