agentleFS
clezcodingclezcoding/awesome-coolify/skills/coolify-diagnose/SKILL.md

coolify-diagnose

Skill0 starsChanged 4 months agoMITView on GitHub

Investigate Coolify application, server, or fleet-wide issues. Use when triaging errors, health checks, or scan results.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    When diagnosis points to missing infrastructure, use recipe actions:

    line 69

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

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

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

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

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

Diagnose tool

Primary entry: MCP diagnose tool (diagnoseActionsCatalog):

Actions: app(query?, uuid?, name?, domain?, limit?) · server(query?, uuid?, name?, ip?, trigger_validate?) · scan(format?, page?, per_page?) · logs(uuid, mode?, lines?, max_chars?)

Workflow

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

    diagnose({ action: "app", uuid: "<uuid>" })
  3. Server path:

    diagnose({ action: "server", uuid: "<server-uuid>" })
  4. Fleet scan path:

    diagnose({ action: "scan" })
  5. Application logs path:

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

    logs combines application diagnosis with a bounded runtime tail. It is application-only in Coolify 4.1.x; service/database logs are unavailable because those REST endpoints do not exist.

  6. Summarize findings by severity and recommend the next remediation step.
  7. If remediation requires redeploy — use coolify-deploy deployment.watch flow:

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

Recipe context

When diagnosis points to missing infrastructure, use recipe actions:

  • create-git-app · create-app-db · create-one-click

Or run coolify-setup for full greenfield wire.

Safety

  • reveal opt-in — pass reveal: true on read/get actions only when the human explicitly needs unmasked secrets or env values. Default responses mask sensitive fields.
  • confirm gates — destructive mutations (delete, emergency redeploy, force overrides) require explicit human approval and confirm: true on the second call after preview.

Example calls

diagnose({ action: "app", uuid: "<uuid>" })

diagnose({ action: "server", uuid: "<server-uuid>", trigger_validate: true })

diagnose({ action: "scan", per_page: 20 })

diagnose({ action: "logs", mode: "full", uuid: "<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.