docker-compose-generator

Generate multi-service Docker Compose files with common stacks (app + DB + Redis + Nginx), volumes, networks, healthchecks, depends_on, environment variables, and profiles.

Quality

75%

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/docker-compose-generator/SKILL.md

Quality

Content

76%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 skill body is highly actionable with complete, executable examples and clean organization, but it lacks explicit validation/verification steps for a workflow that includes destructive operations. Adding a validate-after-generate checkpoint would lift the workflow score.

Suggestions

Add a validation step after scaffolding, e.g. run `docker compose config` to verify the generated file before `docker compose up`.

Flag destructive commands: annotate `docker compose down -v` with a warning that it permanently removes named volumes.

Trim redundancy by dropping the duplicated Prerequisites block or the top blockquote that restates the description verbatim.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable YAML and commands with no padding about basic Docker concepts, though the top blockquote repeats the description and the Prerequisites section duplicates the frontmatter compatibility line.	4 / 5
Actionability	It provides fully executable, copy-paste-ready compose files, an .env.example template, multiple DB variants (Postgres/MySQL/Mongo), and a thorough Common Commands block covering the common cases.	5 / 5
Workflow Clarity	A rough scaffold-to-run sequence exists, but there is no validation checkpoint (e.g. `docker compose config` to validate the generated file) and destructive commands like `docker compose down -v` appear without warnings, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	Content is well organized with clear section headers (Prerequisites, Scaffold, Project Structure, Key Conventions, Essential Patterns, Common Commands, Integration Notes); all material is inline with no bundle files, and the variant examples are reasonably placed though some could live in separate references.	4 / 5
	Total	16 / 20 Passed

Description

75%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 comprehensive about capabilities and occupies a distinct niche, but it lacks an explicit "Use when..." trigger clause, which caps its completeness. Adding trigger guidance and a few synonyms/file extensions would round it out.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to set up Docker Compose, scaffold a multi-service stack, or configure volumes/networks/healthchecks for containers."

Add natural synonyms and file extensions such as "docker-compose.yml", "compose stack", or ".yml" to broaden trigger-term coverage.

Keep the feature list but lead with the single most common user phrasing (e.g. "scaffold a Docker Compose stack") so the trigger reads naturally.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete compose constructs ("volumes, networks, healthchecks, depends_on, environment variables, and profiles" plus named stacks "app + DB + Redis + Nginx"), giving comprehensive coverage of what the skill produces rather than vague language.	5 / 5
Completeness	It clearly states the "what" (generate multi-service compose files with listed features) but provides no "Use when..." clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	It includes natural terms users say ("Docker Compose files", "volumes", "networks", "healthchecks", "depends_on", "environment variables", "profiles"), but omits common synonyms and file extensions like "docker-compose.yml" or ".yml".	4 / 5
Distinctiveness Conflict Risk	"Generate multi-service Docker Compose files" carves out a clear niche with distinct triggers and minimal overlap risk with adjacent skills like Dockerfile or Kubernetes generators.	5 / 5
	Total	17 / 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/docker-compose-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.