CtrlK
BlogDocsLog inGet started
Tessl Logo

docker

Docker expert for containers, Compose, Dockerfiles, and debugging

57

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crates/openfang-skills/bundled/docker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A well-organized, mostly lean Docker reference of curated best practices with concrete commands, but it lacks complete copy-paste examples and any sequenced workflow with validation checkpoints.

Suggestions

Add at least one complete, copy-paste-ready example (e.g., a full multi-stage Dockerfile or docker-compose.yml) to move actionability from guidance to executable.

Trim the Debugging Techniques section of basic commands Claude already knows (docker logs, exec, inspect, stats) and keep only non-obvious debugging tips to improve conciseness.

Add a short sequenced workflow with a validation checkpoint for risky operations (e.g., build -> run healthcheck -> on failure rebuild with --no-cache) to introduce feedback loops.

DimensionReasoningScore

Conciseness

The body is lean bullet-point guidance with no concept-explanation fluff, but the Debugging Techniques section enumerates basic commands Claude already knows (e.g., 'docker logs <container>', 'docker exec -it <container> sh', 'docker inspect').

2 / 3

Actionability

Concrete directives and commands appear throughout ('node:20-alpine', 'USER', 'COPY --from=builder', 'HEALTHCHECK', 'depends_on' with 'condition: service_healthy'), but there is no complete, copy-paste-ready example such as a full multi-stage Dockerfile or docker-compose.yml.

2 / 3

Workflow Clarity

Content is well-organized into topical sections, but it is a best-practices reference rather than a sequenced workflow, with no validation checkpoints or feedback loops for risky operations like rebuilding or force-recreating containers.

2 / 3

Progressive Disclosure

At 39 lines with no bundle files and no need for external references, the skill relies on well-organized sections (Key Principles, Dockerfile Best Practices, Debugging Techniques, Compose Patterns, Pitfalls), which satisfies the under-50-line simple-skill exception.

3 / 3

Total

9

/

12

Passed

Description

72%

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 distinctive, well-triggered description with good natural keywords, but it lacks explicit 'when to use' guidance and leans on domain nouns rather than listing concrete actions.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when building, debugging, or optimizing Docker containers, Compose stacks, or Dockerfiles') to raise completeness from 2 to 3.

Replace the generic 'expert for' framing with concrete verbs (e.g., 'Build, run, debug, and optimize Docker containers, Compose stacks, and Dockerfiles') to improve specificity.

DimensionReasoningScore

Specificity

It names the domain ('containers, Compose, Dockerfiles') and one action-ish term ('debugging'), matching 'Names domain and some actions, but not comprehensive'; it does not list multiple concrete actions like build, run, or optimize.

2 / 3

Completeness

It states what the skill covers ('Docker expert for containers, Compose, Dockerfiles, and debugging') but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2.

2 / 3

Trigger Term Quality

The terms 'Docker', 'containers', 'Compose', 'Dockerfiles', and 'debugging' are exactly the natural keywords a user would say when needing this skill, giving good coverage without jargon.

3 / 3

Distinctiveness Conflict Risk

Docker is a clear, well-defined niche with distinct triggers (Docker, containers, Compose, Dockerfiles), making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

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
RightNow-AI/openfang
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.