dockerfile-generator

Generate optimized, multi-stage Dockerfiles for Node.js, Python, Go, Rust, and Java with layer caching, non-root users, and minimal production images.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./infrastructure/dockerfile-generator/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

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

The body is highly actionable, delivering complete executable Dockerfiles and exact commands across five languages with lean, non-padded prose. Its weaknesses are the lack of an explicit build/verify workflow with validation checkpoints and the monolithic inlining of seven templates that could be split into per-language reference files.

Suggestions

Add an explicit sequenced workflow with a validation checkpoint, e.g. build -> run a smoke test / docker scout scan -> only then tag and push.

Move per-language Dockerfile templates into separate reference files (e.g. references/node.md, references/python.md) and keep SKILL.md as an overview with one-level-deep links, reducing inline token load.

Trim the near-duplicate pnpm template (or note only the deltas vs the npm template) and drop the trivial 'touch Dockerfile' scaffold to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Prose is lean and assumes Claude's knowledge (no 'Docker is...' explanations); the payload is code. Minor redundancy exists (pnpm template largely duplicates npm; 'touch Dockerfile' scaffold is trivial).	4 / 5
Actionability	Provides multiple complete, copy-paste-ready Dockerfiles across the common languages plus exact docker/buildx/scout commands, covering the common cases fully.	5 / 5
Workflow Clarity	An implied scaffold -> build -> run -> scan flow exists via the command catalog, but there is no explicit sequenced workflow and no validation/verification checkpoint (e.g. 'verify the image builds and scout passes before proceeding').	3 / 5
Progressive Disclosure	Section headers are clear and well-organized, but seven full Dockerfile templates are inlined in one file with no references to per-language detail files, and no bundle files exist to offload the bulk.	3 / 5
	Total	15 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 is concrete and specific, clearly scoping a Dockerfile-generation niche across five languages with named optimization techniques. Its main weakness is the absence of any 'when to use' trigger guidance, which caps completeness. Adding an explicit 'Use when...' clause would lift the description to the top band.

Suggestions

Append a 'Use when...' trigger clause, e.g. 'Use when the user asks to containerize a Node.js, Python, Go, Rust, or Java app, or needs a production Dockerfile/Docker image.'

Add natural synonyms users say ('containerize', 'Docker image', 'container') to broaden trigger-term coverage.

Consider a second concrete verb (e.g. 'Generate and optimize ... Dockerfiles') to strengthen the specificity of actions beyond a single 'Generate' verb.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Generate optimized, multi-stage Dockerfiles') plus five target languages and four concrete optimization attributes (layer caching, non-root users, minimal production images), giving broad coverage.	4 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Dockerfiles', 'Node.js', 'Python', 'Go', 'Rust', 'Java'), though common variations like 'containerize', 'Docker image', and 'container' are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Dockerfile generation for specific languages) with distinct triggers, with only minor overlap risk against a general containerization or docker-compose skill.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: infrastructure/dockerfile-generator/SKILL.md
Commit: 181fcbc

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.