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.
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./infrastructure/docker-compose-generator/SKILL.mdQuality
Discovery
67%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 excels at specificity with comprehensive technical details about Docker Compose capabilities and components. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill. Adding natural user language variations would improve discoverability.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user asks to create docker-compose.yml files, set up containerized applications, or configure multi-container environments'
Include common user phrases and file extensions like 'docker-compose.yml', 'containerize', 'container setup', or 'microservices deployment'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and components: 'multi-service Docker Compose files', 'common stacks (app + DB + Redis + Nginx)', 'volumes, networks, healthchecks, depends_on, environment variables, and profiles'. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with detailed capabilities, but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Docker Compose', 'Redis', 'Nginx', 'healthchecks', but missing common user variations like 'docker-compose.yml', 'containerization', 'container orchestration', or simpler terms users might say. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on Docker Compose with detailed component list; unlikely to conflict with general Docker skills or other infrastructure tools due to the explicit multi-service and stack focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent concrete examples and efficient token usage. The YAML configurations are production-ready with proper healthchecks, networks, and environment variable patterns. However, it lacks explicit validation workflows (e.g., validating compose files before running) and could benefit from better progressive disclosure by moving database variants to a separate reference file.
Suggestions
Add a validation step before running compose: 'docker compose config' to validate YAML syntax and variable interpolation
Include troubleshooting guidance for common failures (healthcheck failures, port conflicts, volume permission issues)
Consider moving database variants (MySQL, MongoDB) to a separate DATABASES.md reference file to reduce main file length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information without explaining basic Docker concepts. Every section serves a clear purpose with no padding or unnecessary explanations. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready YAML configurations and bash commands. The examples are complete with proper syntax, environment variable handling, healthchecks, and all necessary configuration details. | 3 / 3 |
Workflow Clarity | While the structure is logical and commands are well-organized, there are no explicit validation checkpoints or feedback loops. Missing verification steps like 'docker compose config' to validate YAML before running, or troubleshooting guidance when services fail healthchecks. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the file is quite long (~200 lines of YAML examples). The Integration Notes reference other skills but the main content could benefit from splitting database variants and optional patterns into separate reference files. | 2 / 3 |
Total | 10 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.