CtrlK
BlogDocsLog inGet started
Tessl Logo

coolify-deployment

Deploys applications, databases, and services on self-hosted Coolify instances, manages environments and env vars, runs infrastructure diagnostics, and performs batch operations. Use when deploying apps to Coolify, managing Coolify servers, debugging deployment issues, setting up databases, or managing Coolify infrastructure.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

A dense, highly actionable reference that earns top marks for actionability and structure. Its main weakness is workflow clarity: destructive and batch operations lack explicit validation checkpoints, and the inline version pin costs a conciseness point.

Suggestions

Add an explicit validation feedback loop for destructive/batch operations — e.g. after a deploy or bulk_env_update, verify status (get_infrastructure_overview / find_issues) and retry on failure — so workflow_clarity can exceed the cap of 3.

Move the time-sensitive 'Requires Coolify ≥ v4.0.0-beta.411' version pin into a dedicated 'Version requirements' or 'Deprecations' section rather than inlining it in a gotcha bullet.

Surface a short ordered workflow (overview → diagnose → change → restart → verify) at the top so the existing steps read as a single sequenced process rather than isolated bullets.

DimensionReasoningScore

Conciseness

The body is lean and dense with no padding or explanation of concepts Claude already knows, but the inline version requirement 'Requires Coolify ≥ v4.0.0-beta.411' is time-sensitive information not placed in a deprecated/old-patterns section, which the guideline penalizes.

4 / 5

Actionability

Guidance is fully executable — exact tool syntax ('env_vars → control action="restart"'), a copy-paste curl webhook command, and precise magic-variable rules ('SERVICE_URL_APP_3000' vs '$SERVICE_URL_APP') covering the common cases.

5 / 5

Workflow Clarity

Some sequencing exists ('Start every session with get_infrastructure_overview', env-var change → restart, follow HATEOAS _actions), but batch operations (bulk_env_update) and destructive operations (force_rebuild, deleting ports:) lack an explicit validate→fix→retry feedback loop, capping the score at 3 per the rubric.

3 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (# Coolify Deployment, ## MCP tools, ## Docker Compose gotchas) and a single external docs link; no nested references and no bundle files, so the simple-skill exception permits a top mark.

5 / 5

Total

17

/

20

Passed

Description

92%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.

A strong, third-person description that pairs a concrete capability list with an explicit 'Use when' trigger clause scoped to Coolify. Coverage is comprehensive and conflict risk is low; only minor synonym breadth in the trigger terms keeps it just short of a perfect mark.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the domain — 'Deploys applications, databases, and services', 'manages environments and env vars', 'runs infrastructure diagnostics', 'performs batch operations' — giving comprehensive coverage rather than vague claims.

5 / 5

Completeness

Explicitly answers both what ('Deploys…manages…runs…performs') and when ('Use when deploying apps to Coolify, managing Coolify servers, debugging deployment issues, setting up databases, or managing Coolify infrastructure') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('deploying apps to Coolify', 'debugging deployment issues', 'setting up databases', 'managing Coolify servers'), but a few common variations (e.g. 'env vars', 'infrastructure') are only lightly represented and no synonyms beyond 'Coolify' appear.

4 / 5

Distinctiveness Conflict Risk

Scoped to self-hosted Coolify with Coolify-specific triggers, occupying a clear niche with minimal overlap risk against generic deploy or DB skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.