coolify-compose
Convert Docker Compose files to Coolify templates. Use when creating Coolify services, converting docker-compose.yml for Coolify deployment, working with SERVICE_URL/SERVICE_PASSWORD magic variables, or troubleshooting Coolify compose errors.
72
87%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its niche (Docker Compose to Coolify conversion) and provides explicit trigger guidance with relevant keywords. The main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond just 'convert' — e.g., mapping volumes, configuring environment variables, generating template YAML. Overall it performs well across all dimensions.
Suggestions
Expand the capability description with more concrete actions, e.g., 'Convert Docker Compose files to Coolify templates, map environment variables to magic variables (SERVICE_URL, SERVICE_PASSWORD), configure persistent storage, and validate template syntax.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Docker Compose to Coolify templates) and mentions some actions like converting and troubleshooting, but doesn't list multiple concrete actions beyond 'convert'. Working with magic variables and troubleshooting errors are somewhat specific but not deeply detailed. | 2 / 3 |
Completeness | Clearly answers both 'what' (convert Docker Compose files to Coolify templates) and 'when' with an explicit 'Use when...' clause listing four distinct trigger scenarios: creating Coolify services, converting docker-compose.yml, working with magic variables, and troubleshooting compose errors. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Docker Compose', 'Coolify', 'docker-compose.yml', 'Coolify deployment', 'SERVICE_URL', 'SERVICE_PASSWORD', 'magic variables', 'Coolify compose errors'. These are highly specific and natural terms a user working in this domain would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very clear niche. The combination of 'Coolify' and 'Docker Compose' conversion is specific enough that it would be very unlikely to conflict with generic Docker or deployment skills. The mention of Coolify-specific concepts like magic variables further distinguishes it. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, actionable guidance for converting Docker Compose files to Coolify templates. Its greatest strengths are the concrete before/after YAML examples, the structured conversion checklist, and the clear decision framework for choosing deployment modes. The only notable weakness is moderate verbosity — the content could be tightened by consolidating the deployment mode comparison tables and reducing some repetition in the config file mounting examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally efficient and avoids explaining basic Docker Compose concepts, but it's quite long (~300 lines) with some redundancy. The deployment modes section has overlapping tables, and some patterns (like the config file mounting) are shown in multiple places. The feature comparison tables for raw vs repository mode could be consolidated. | 2 / 3 |
Actionability | Excellent actionability throughout. Every section provides concrete, copy-paste-ready YAML examples with clear before/after comparisons. The conversion checklist gives specific steps with executable code, the magic variables reference includes exact syntax, and the troubleshooting table maps problems to specific solutions. | 3 / 3 |
Workflow Clarity | The conversion checklist (steps 0-6) provides a clear, sequenced workflow. Step 0 acts as a decision checkpoint (build vs raw mode), health checks serve as validation steps, and the depends_on with conditions ensures proper service ordering. The 'Which Mode to Use?' decision table adds a useful triage step before starting. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled references to deeper content: examples are organized by complexity (simple/, with-database/, multi-service/), magic variables reference is linked to a separate file, and categories have their own reference. The structure flows from quick start → checklist → details → patterns → troubleshooting → examples → references. However, bundle files weren't provided to verify paths exist, but the structure is sound. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- joshuadavidthomas/agent-skills
- Commit
40067f1
- 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.