generating-docker-compose-files

Execute use when you need to work with Docker Compose. This skill provides Docker Compose file generation with comprehensive guidance and automation. Trigger with phrases like "generate docker-compose", "create compose file", or "configure multi-container app".

Quality

56%

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 ./plugins/devops/docker-compose-generator/skills/generating-docker-compose-files/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

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 well-organized, mostly lean instruction set with concrete Compose keys and a validation step, but it stays at 2 across the board: no inline executable example, no explicit fix-and-revalidate loop, and a disconnect between the SKILL.md and the bundled template/examples/scripts it never points to.

Suggestions

Reference the actual bundle files inline, e.g. point to assets/compose_template.yml and assets/example_app_architectures.md in the Instructions/Examples sections, and replace the non-existent start.sh/stop.sh/logs.sh with the real scripts/validate_compose.sh, generate_env_file.py, and deploy.sh.

Add a short copy-paste docker-compose.yml snippet (services + networks + volumes + healthcheck) so the guidance is executable, not just directive.

Turn step 10 into an explicit feedback loop: 'Run docker compose config; if it reports errors, fix them and re-validate before proceeding.'

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with a concrete 10-step instruction list and no over-explanation of Docker concepts, but the Prerequisites section includes items Claude already knows ('Sufficient disk space and memory', 'Understanding of service dependencies') and the Overview carries residual fluff ('comprehensive guidance and automation').	2 / 3
Actionability	Steps reference real Compose keys (depends_on, deploy.resources.limits) and a real command (docker compose config), but there is no executable copy-paste YAML example in the body and steps are high-level directives ('Define each service with image or build context, port mappings, and environment variables') rather than complete specifics.	2 / 3
Workflow Clarity	A clear 10-step sequence with an explicit final validation step (step 10) and an error table exists, but there is no validate->fix->revalidate feedback loop in the workflow itself — the error handling is a separate reference table rather than an inline checkpoint loop.	2 / 3
Progressive Disclosure	The body is well-sectioned (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources), but the existing bundle files (compose_template.yml, example_app_architectures.md, validate_compose.sh, generate_env_file.py, deploy.sh) are never referenced or linked, and the Output section names non-existent scripts (start.sh, stop.sh, logs.sh) — the bundle is effectively orphaned.	2 / 3
	Total	8 / 12 Passed

Description

62%Weight 40%Scale 1-3

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 has good trigger terms and a clear niche, but its capability statement is a single fluffy action rather than concrete enumerated capabilities, and the malformed 'Execute use when' opening plus second-person voice weaken it.

Suggestions

Replace 'comprehensive guidance and automation' with 2-3 concrete actions, e.g. 'Define services, networks, volumes, health checks, and environment overrides for multi-container apps'.

Fix the malformed opener 'Execute use when' to a clean third-person 'Use when...' clause, and drop the second-person 'you need to work with' to avoid the voice penalty.

Lead with the concrete 'what' before the trigger phrases so the capability list is unambiguous.

Dimension	Reasoning	Score
Specificity	Only one concrete action is named ('Docker Compose file generation'), padded with vague fluff ('comprehensive guidance and automation'); the second-person phrasing 'use when you need to work with' triggers the -1 specificity penalty per the rubric, dropping it from a base of 2.	1 / 3
Completeness	It does provide an explicit 'when' via the trigger phrases, but the 'what' is stated only as fluffy over-claim ('comprehensive guidance and automation') rather than concrete capabilities, and the opening 'Execute use when' is malformed — not the clear, concrete what+when of a 3.	2 / 3
Trigger Term Quality	Lists three natural user phrases ('generate docker-compose', 'create compose file', 'configure multi-container app') that a user would plausibly say, giving good coverage of common variations rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Docker Compose file generation is a clear niche with distinct, specific triggers unlikely to overlap with or fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/devops/docker-compose-generator/skills/generating-docker-compose-files/SKILL.md
Commit: 4c47e33

Reviewed: 16 minutes 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.