Content
80%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |