agentleFS
Sign inStart free
clezcodingclezcoding/awesome-coolify/skills/coolify-deploy/SKILL.md

coolify-deploy

Skill0 starsChanged 4 months agoMITView on GitHub

Deploy a Coolify application and monitor until terminal status. Use when triggering deployments or watching build progress.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. haythamasalama/skills★ 0same name
    2. velandia3110/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check system({ action: "version" }) before relying on optional capability flags.

    line 42
  2. Distinctive:

    After recipe create, deploy with the workflow above.

    line 58
  3. Very specific:

    Use reveal: true only when the human opts in to sensitive log or env content.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Coolify Deploy

Install this skill pack (Cursor, Claude Code, Codex):

npx skills add clezcoding/awesome-coolify -a cursor -a claude-code -a codex

MCP prompt analog: deploy (src/mcp/prompts.ts)

Related skills: coolify-setup · coolify-diagnose · coolify-incident

Deploy workflow

  1. Resolve UUID — from args, .coolify/manifest.json, or ask the user.

  2. Trigger deployment — capture deployment_uuid with wait: false:

    application({ action: "deploy", uuid: "<uuid>", wait: false })

  3. Monitor with bounded watch — primary path (not wait: true):

    deployment({ action: "watch", deployment_uuid: "<deployment_uuid>", timeout: 300 })
  4. On COOLIFY_WATCH_TIMEOUT — re-call deployment.watch with the same deployment_uuid. Raise timeout if builds are slow (max 1800s).
  5. On failed or cancelled-by-user — surface the error and logs hint; do not treat as success.

Legacy: application.deploy wait:true is back-compat only. Prefer deployment.watch for bounded polling with backoff.

Logs and capabilities

Check system({ action: "version" }) before relying on optional capability flags.

  • Fetch build/deployment output with deployment.logs: deployment({ action: "logs", deployment_uuid: "<deployment_uuid>" }).
  • Fetch or follow application runtime output with application.logs: application({ action: "logs", uuid: "<uuid>", follow: true }).
  • Coolify 4.1.x has no service/database log endpoints.

Recipe shortcuts

Greenfield provisioning uses the recipe tool (recipeActionsCatalog):

  • create-git-app(server_uuid, git_repository, git_branch, repo_path?, build_pack?)
  • create-app-db(server_uuid, app_name, db_name, db_engine, env_key?)
  • create-one-click(server_uuid, type, instant_deploy?)

After recipe create, deploy with the workflow above.

Safety

  • confirm gates — confirm before force deploy or destructive lifecycle actions when the user did not explicitly request them.
  • Use reveal: true only when the human opts in to sensitive log or env content.

Example calls

application({ action: "deploy", uuid: "<uuid>", wait: false })

deployment({ action: "watch", deployment_uuid: "<deployment_uuid>", timeout: 300 })

// After COOLIFY_WATCH_TIMEOUT:
deployment({ action: "watch", deployment_uuid: "<deployment_uuid>", timeout: 600 })

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free