What is coolify-diagnose?

A troubleshooting guide for Coolify applications and servers. Coolify is a platform for deploying and managing applications, databases, and servers.

Use it to diagnose an application, server, or fleet-wide scan in Coolify. It covers finding identifiers, validating systems, reviewing bounded application log tails, and summarizing findings.

It provides a structured way to investigate failed health checks, errors, scans, and runtime logs instead of checking each part randomly. It also distinguishes application logs from unavailable service or database logs.

coolify-diagnose — Skill for Claude Code and Codex by clezcoding

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add clezcoding/awesome-coolify --skill coolify-diagnose

Clone the repo

git clone --depth 1 https://github.com/clezcoding/awesome-coolify

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/clezcoding/awesome-coolify/coolify-diagnose/github.svg)](https://agentmods.dev/skills/clezcoding/awesome-coolify/coolify-diagnose)

Your own site

<a href="https://agentmods.dev/skills/clezcoding/awesome-coolify/coolify-diagnose"><img src="https://agentmods.dev/badge/skills/clezcoding/awesome-coolify/coolify-diagnose/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/clezcoding/awesome-coolify/coolify-diagnose"><img src="https://agentmods.dev/badge/skills/clezcoding/awesome-coolify/coolify-diagnose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 715 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00032	$0.00715
Opus 5.5	$0.00013	$0.00286
Sonnet 5.5	$0.00006	$0.00143
Haiku 4.5	$0.00003	$0.00072

Measured 1mo ago against content hash b30650d4e48d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coolify-diagnose scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/coolify-diagnose/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

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

Application path:

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

Server path:

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

Fleet scan path:
```
diagnose({ action: "scan" })
```
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.
Summarize findings by severity and recommend the next remediation step.

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.

Read the full file on GitHub · 91 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 91 lines · 32 tokens per session scan A b30650d4e48d

Subscribe to this mod's changes

coolify-diagnose is a skill published in the GitHub repository clezcoding/awesome-coolify (0 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 715 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Debugging DevOps and cloud TypeScript coolify mcp model-context-protocol self-hosted

debugging-executions

Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error. Also load when a live run you started for the user fails with an error from…

n8n-io/n8n · 86 tokens

n8n-docs-assistant

Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs. Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior, especially credential setup questions — including which OAuth scopes or permissions a provider app needs.

n8n-io/n8n · 71 tokens

runtime-diagnostics

Investigate Pioneer Gateway or desktop CPU, memory, slow work, queues, and runtime stalls using process metrics, local snapshots, bounded native profiles, and exact release symbols. Use for Pioneer performance diagnosis and interpreting its diagnostic artifacts.

pioneerdotai/pioneer · 49 tokens

coolify-diagnose