CtrlK
BlogDocsLog inGet started
Tessl Logo

docker

Guide for using Docker - a containerization platform for building, running, and deploying applications in isolated containers. Use when containerizing applications, creating Dockerfiles, working with Docker Compose, managing images/containers, configuring networking and storage, optimizing builds, deploying to production, or implementing CI/CD pipelines with Docker.

71

Quality

71%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./claude/skills/docker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, uses natural trigger terms that users would actually say, includes an explicit 'Use when...' clause with comprehensive scenarios, and has distinct Docker-specific terminology that minimizes conflict risk with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'containerizing applications, creating Dockerfiles, working with Docker Compose, managing images/containers, configuring networking and storage, optimizing builds, deploying to production, implementing CI/CD pipelines'.

3 / 3

Completeness

Clearly answers both what ('containerization platform for building, running, and deploying applications in isolated containers') and when with explicit 'Use when...' clause listing eight specific trigger scenarios.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'Docker', 'Dockerfiles', 'Docker Compose', 'containers', 'images', 'networking', 'CI/CD pipelines', 'containerizing' - these are all terms users naturally use when working with Docker.

3 / 3

Distinctiveness Conflict Risk

Clear niche focused specifically on Docker containerization with distinct triggers like 'Dockerfiles', 'Docker Compose', 'containers', 'images' - unlikely to conflict with other skills due to Docker-specific terminology.

3 / 3

Total

12

/

12

Passed

Implementation

42%

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

This skill is highly actionable with excellent, executable code examples covering Docker comprehensively. However, it severely violates token efficiency by being a massive reference document rather than a focused skill guide. The content would be far more effective split into a concise overview with references to detailed topic files.

Suggestions

Split into SKILL.md overview (under 100 lines) with references to separate files: DOCKERFILES.md, COMPOSE.md, PRODUCTION.md, TROUBLESHOOTING.md

Remove explanatory content about what containers/images/networks are - Claude knows these concepts

Add explicit validation steps to workflows, e.g., 'After building, verify with: docker run --rm myapp:1.0 --version'

Move the language-specific Dockerfiles to a separate EXAMPLES.md file with just the quick reference table in the main skill

DimensionReasoningScore

Conciseness

Extremely verbose at 700+ lines, explaining many concepts Claude already knows (what containers are, what images are, basic networking concepts). Includes extensive reference material that belongs in separate files, not inline.

1 / 3

Actionability

Provides fully executable, copy-paste ready code examples throughout. Dockerfiles are complete and production-ready, commands are specific with all necessary flags, and examples cover real-world scenarios.

3 / 3

Workflow Clarity

Steps are listed clearly for individual tasks (building, running, compose), but lacks explicit validation checkpoints for multi-step processes. The production checklist is helpful but doesn't integrate validation into workflows.

2 / 3

Progressive Disclosure

Monolithic wall of text with everything inline. Content that should be in separate files (language-specific Dockerfiles, CI/CD examples, troubleshooting guide) is all embedded. References to external docs at the end don't help with internal organization.

1 / 3

Total

7

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1017 lines); consider splitting into references/ and linking

Warning

Total

10

/

11

Passed

Repository
einverne/dotfiles
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.