CtrlK
BlogDocsLog inGet started
Tessl Logo

docker-best-practices

Docker best practices including multi-stage builds, compose patterns, image optimization, and security

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/docker-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The body is a lean, highly actionable Docker reference with executable examples and no wasted tokens, excelling in conciseness and actionability. Its main gap is the absence of an explicit sequenced workflow with validation checkpoints, which limits workflow clarity.

Suggestions

Add a short ordered workflow with validation checkpoints, e.g. '1. Build with target runtime 2. Verify size with docker history/dive 3. Test HEALTHCHECK 4. Fix and rebuild if checks fail', to turn the reference into a guided process.

Connect the closing Checklist to the workflow as an explicit validate-before-ship gate rather than a standalone list.

DimensionReasoningScore

Conciseness

The body is code-first with terse, purposeful prose ('Separate dependency installation from build steps.'; 'Combine RUN commands to reduce layers.') and no explanation of basic Docker concepts, so every token earns its place.

3 / 3

Actionability

It provides fully executable Dockerfiles, a complete compose YAML, copy-paste bash commands ('docker history --human --no-trunc <image>', 'dive <image>'), and a concrete .dockerignore — all directly runnable.

3 / 3

Workflow Clarity

The content is organized as a reference collection with a closing checklist, but there is no sequenced multi-step workflow with explicit validation checkpoints or a build→verify→fix feedback loop, so it sits below the 'clear sequence with explicit validation' anchor.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single SKILL.md is well-organized into clearly headed sections (Multi-Stage Build, Docker Compose, .dockerignore, Image Optimization, Anti-Patterns, Checklist) with no nested references and easy navigation.

3 / 3

Total

11

/

12

Passed

Description

57%

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, distinctive Docker niche but reads as a topic list rather than an action statement and lacks any explicit 'when to use' trigger guidance. Adding verb-led actions and a 'Use when...' clause would lift completeness and trigger-term quality.

Suggestions

Lead with concrete actions, e.g. 'Write and optimize Dockerfiles, structure multi-stage builds, configure docker-compose services, and harden container images.'

Add an explicit trigger clause: 'Use when writing or reviewing Dockerfiles, docker-compose files, or container images, or when the user mentions Docker, containers, or image optimization.'

Include high-frequency trigger terms users actually say — 'Dockerfile', 'container', and 'docker-compose' — alongside the existing keywords.

DimensionReasoningScore

Specificity

The description names the Docker domain and several specific sub-areas ('multi-stage builds, compose patterns, image optimization, and security'), but these are topic labels rather than concrete verb-led actions, so it does not reach the 'multiple specific concrete actions' anchor.

2 / 3

Completeness

It clearly states what the skill covers ('Docker best practices including...') but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.

2 / 3

Trigger Term Quality

Natural terms like 'Docker', 'multi-stage builds', 'compose patterns', and 'image optimization' are present, but common variations a user would actually say — 'Dockerfile', 'container', 'docker-compose' — are missing, so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The Docker-specific framing with concrete sub-domains (multi-stage builds, compose, image optimization, security) forms a clear niche unlikely to trigger for unrelated skills.

3 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rohitg00/awesome-claude-code-toolkit
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.