CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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, highly actionable skill that provides comprehensive guidance for converting Docker Compose files to Coolify templates. Its greatest strengths are the concrete before/after examples, clear conversion checklist, and practical troubleshooting table. The main weakness is length — at ~300 lines the body content could benefit from moving some reference material (health check patterns, env var syntax) into the referenced files to improve progressive disclosure.

Suggestions

Move the 'Health Check Patterns' and 'Environment Variable Syntax' sections into reference files (e.g., references/health-checks.md) and link to them, keeping the main SKILL.md as a tighter overview

Consolidate the two deployment mode sections — the feature comparison tables and 'Which Mode to Use?' table have overlapping information that could be merged into a single decision table

DimensionReasoningScore

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 twice across sections. 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 for converting compose files. The decision trees for deployment mode selection and example selection serve as effective validation checkpoints. The 'Declaration vs Reference (Critical)' section explicitly calls out a common error point with clear correct/incorrect examples.

3 / 3

Progressive Disclosure

The skill references external files (references/magic-variables.md, references/categories.md, examples/simple/, examples/with-database/, examples/multi-service/) which is good structure, but no bundle files were provided to verify these exist. The main SKILL.md itself is quite long and some content (like the full health check patterns and environment variable syntax sections) could potentially be moved to reference files to keep the overview leaner.

2 / 3

Total

10

/

12

Passed

Description

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 with excellent trigger terms and completeness. It clearly identifies its niche (Docker Compose to Coolify conversion) and provides explicit 'Use when' guidance with multiple trigger scenarios. The main weakness is that the specificity of concrete actions could be slightly improved by listing more specific capabilities beyond 'convert' and 'troubleshoot'.

Suggestions

Add more specific concrete actions to improve specificity, e.g., 'Convert Docker Compose files to Coolify templates, map environment variables to magic variables (SERVICE_URL, SERVICE_PASSWORD), configure service dependencies, and validate Coolify-compatible compose syntax.'

DimensionReasoningScore

Specificity

Names the domain (Docker Compose to Coolify templates) and mentions some specific elements like SERVICE_URL/SERVICE_PASSWORD magic variables, but doesn't list multiple concrete actions beyond 'convert'. The troubleshooting mention adds some breadth but remains somewhat vague about what specific actions are performed.

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, or 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 terms a user working in this domain would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a very clear niche — the combination of Docker Compose and Coolify is specific enough that it's unlikely to conflict with generic Docker skills or other deployment tools. The mention of Coolify-specific concepts like magic variables further narrows the scope.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
joshuadavidthomas/agent-skills
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.