docker
Docker containerization best practices for building, securing, and deploying containers.
37
27%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docker/SKILL.mdQuality
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 a clear technical domain (Docker) but lacks the explicit trigger guidance required for Claude to reliably select this skill. It uses appropriate third-person voice and mentions key activities, but the actions are too high-level and the absence of a 'Use when...' clause significantly limits its effectiveness for skill selection.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Dockerfiles, container images, docker-compose, container security, or deploying with Docker'
Expand specific actions to include concrete tasks like 'write Dockerfiles, configure multi-stage builds, optimize image sizes, set up docker-compose configurations'
Include more natural trigger terms users might say: 'Dockerfile', 'docker-compose', 'container image', '.dockerfile', 'docker build'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Docker containerization) and mentions general action categories (building, securing, deploying), but doesn't list specific concrete actions like 'write Dockerfiles', 'configure multi-stage builds', or 'set up container registries'. | 2 / 3 |
Completeness | Describes what (Docker best practices for building/securing/deploying) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Docker', 'containerization', 'containers' which are relevant keywords, but misses common variations users might say like 'Dockerfile', 'docker-compose', 'container image', 'docker build', or 'kubernetes'. | 2 / 3 |
Distinctiveness Conflict Risk | Docker/containerization is a specific enough domain to avoid conflicts with most skills, but 'deploying' could overlap with general deployment or CI/CD skills, and 'best practices' is vague enough to potentially conflict with other DevOps-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a checklist of Docker best practices than actionable guidance. It lacks concrete examples (no actual Dockerfile snippets, docker-compose.yml examples, or CLI commands), making it difficult for Claude to execute specific tasks. The content would benefit significantly from executable code examples and step-by-step workflows.
Suggestions
Add concrete Dockerfile examples showing multi-stage builds, layer optimization, and non-root user configuration
Include a complete docker-compose.yml example demonstrating the recommended patterns
Provide a step-by-step workflow for building and deploying a secure container image with validation checkpoints (e.g., build -> scan -> test -> push)
Add specific CLI commands for common operations like vulnerability scanning, image tagging, and pushing to registries
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some guidance Claude already knows (e.g., 'Use official base images when possible', 'Never store secrets in images'). Could be tightened by removing obvious best practices. | 2 / 3 |
Actionability | The skill provides only abstract guidance with no concrete code examples, commands, or executable Dockerfile snippets. Statements like 'Use multi-stage builds' and 'Combine RUN commands' describe rather than instruct with copy-paste ready examples. | 1 / 3 |
Workflow Clarity | No clear sequenced workflows are provided. The content lists best practices as bullet points without showing how to implement them step-by-step or providing validation checkpoints for building and deploying containers. | 1 / 3 |
Progressive Disclosure | The content has reasonable section organization with clear headers, but it's a monolithic document with no references to external files for detailed topics like security scanning, CI/CD pipelines, or compose examples that could benefit from separate detailed guides. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
62%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed | |
- Repository
- mindrally/skills
- Commit
47f47c1
- Reviewed
Table of Contents
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.