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

coolify-incident

Skill0 starsChanged 4 months agoMITView on GitHub

Triage and respond to Coolify incidents with diagnose, logs, restart, and emergency actions. Use when production is down or degraded.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When redeploying, use coolify-deploy watch-primary flow:

    line 67
  2. Very specific:

    Never treat failed or cancelled-by-user deployment status as success.

    line 88

≈ “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 Incident

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

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

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

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

Incident response workflow

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

  2. Check capabilities:

    system({ action: "version" })

  3. Triage and tail application logs:

    diagnose({ action: "logs", mode: "full", uuid: "<uuid>" })

  4. Follow a live application symptom when supported:

    application({ action: "logs", uuid: "<uuid>", follow: true })

  5. On build or deploy suspicion, inspect deployment logs:

    deployment({ action: "logs", deployment_uuid: "<deployment-uuid>" })

    Coolify 4.1.x supports application runtime and deployment logs. Service/database logs are unavailable because their REST endpoints do not exist.

  6. Attempt least-destructive recovery — restart:

    application({ action: "restart", uuid: "<uuid>" })

  7. If restart is insufficient — ask the human before destructive actions. Preview emergency redeploy:

    emergency({ action: "redeploy_project", project_uuid: "<project-uuid>", confirm: false })

    Retry with confirm: true only after explicit human approval.

  8. Report incident status, actions taken, and recommended follow-up.

Deploy watch after recovery

When redeploying, use coolify-deploy watch-primary flow:

application({ action: "deploy", uuid: "<uuid>", wait: false })
deployment({ action: "watch", deployment_uuid: "<deployment_uuid>", timeout: 300 })

On COOLIFY_WATCH_TIMEOUT, re-call deployment.watch with the same deployment_uuid.

Recipe shortcuts

For net-new resources during incident recovery:

  • recipe({ action: "create-git-app", ... })
  • recipe({ action: "create-app-db", ... })
  • recipe({ action: "create-one-click", ... })

Safety

  • confirm gates — all destructive emergency actions require preview with confirm: false, then human approval before confirm: true.
  • reveal opt-in — use reveal: true on logs/env reads only when the human needs unmasked sensitive content.
  • Never treat failed or cancelled-by-user deployment status as success.

Example calls

system({ action: "version" })

diagnose({ action: "logs", mode: "full", uuid: "<uuid>" })

application({ action: "logs", uuid: "<uuid>", follow: true })

deployment({ action: "logs", deployment_uuid: "<deployment-uuid>" })

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