jbvc/docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.
59
59%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
32%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 identifies its domain (Docker/Docker Compose) and lists relevant topic areas, but reads more like a table of contents than an actionable skill description. It lacks concrete actions (verbs describing what the skill does) and entirely omits a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Dockerfiles, docker-compose.yml configuration, container debugging, or setting up local multi-service environments.'
Replace topic categories with concrete actions, e.g., 'Writes Dockerfiles, configures docker-compose.yml files, debugs container networking, sets up volume mounts, and implements container security best practices.'
Include common file and term variations users might mention, such as 'Dockerfile', 'docker-compose.yml', '.env files', 'container images', 'ports', 'build context'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Docker/Docker Compose) and lists several topic areas (container security, networking, volume strategies, multi-service orchestration), but these are categories rather than concrete actions. It doesn't specify what actions are performed, like 'write Dockerfiles', 'configure compose files', or 'debug container networking'. | 2 / 3 |
Completeness | Describes the 'what' at a high level (Docker patterns for various concerns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak (topics rather than actions), so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes good keywords like 'Docker', 'Docker Compose', 'container', 'networking', 'volume', and 'multi-service orchestration' that users might naturally use. However, it misses common variations like 'Dockerfile', 'docker-compose.yml', 'containers', 'ports', 'images', or 'build'. | 2 / 3 |
Distinctiveness Conflict Risk | The Docker/Docker Compose focus provides some distinctiveness, but 'local development', 'networking', and 'security' are broad terms that could overlap with general DevOps, infrastructure, or security-focused skills. The lack of explicit triggers increases conflict risk. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference-style skill with excellent actionability — nearly every section provides complete, executable examples. Its main weaknesses are the monolithic structure (could benefit from splitting advanced topics into separate files) and the lack of explicit workflow sequences with validation checkpoints, particularly for operations like building and deploying containers. Some minor verbosity in restating patterns across sections.
Suggestions
Add explicit workflow sequences with validation steps, e.g., after writing a Dockerfile: build → inspect image size → run → verify healthcheck → test connectivity.
Split advanced sections (security hardening, networking patterns, volume strategies) into separate referenced files to improve progressive disclosure and reduce the monolithic feel.
Remove the anti-patterns section or condense it significantly — most points are already demonstrated in the examples above (non-root user, pinned tags, secrets management).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with well-commented YAML/Dockerfile examples, but some sections are slightly verbose. The anti-patterns section restates things already covered (e.g., non-root user, pinning tags), and inline comments sometimes explain things Claude already knows. However, it's not egregiously padded. | 2 / 3 |
Actionability | Excellent actionability throughout — complete, copy-paste-ready docker-compose.yml files, multi-stage Dockerfiles, bash commands for debugging, and concrete networking/volume configurations. Every section provides executable examples rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | The skill presents patterns and reference material rather than sequenced workflows. There are no explicit validation checkpoints — for example, after building a Dockerfile or modifying compose files, there's no 'verify it works' step. The debugging section lists commands but doesn't integrate them into a troubleshooting workflow with feedback loops. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping, but it's a long monolithic file (~200+ lines of substantive content). Advanced topics like security hardening, networking patterns, and volume strategies could be split into referenced files. No external references are provided. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents