← ClaudeAtlas

coolify-clilisted

Operate Coolify instances through the official coollabsio/coolify-cli. Use for CLI setup and authentication, resource inspection, deployments, logs, application configuration, environment variables, databases, services, backups, and infrastructure management in Coolify.
itsjavi/skills · ★ 1 · DevOps & Infrastructure · score 74
Install: claude install-skill itsjavi/skills
# Coolify CLI Use the official `coolify` executable for the requested Coolify operation. Keep this skill portable across projects and instances; discover names, UUIDs, credentials, branches, and environments from the current task. ## Establish the target 1. Check `coolify version` and the relevant command's `--help`. The version command is a subcommand, not `--version`. If installation or authentication is missing, read [setup.md](references/setup.md). 2. Inspect saved contexts with `coolify context list`. Select the instance established by the request and project configuration. If several targets remain plausible, ask for the missing target before issuing requests to one. 3. Use `--context "$COOLIFY_CONTEXT"` on remote operations. This variable represents the resolved saved context name. Avoid changing the persistent default just to execute a task. 4. Verify connectivity with `coolify --context "$COOLIFY_CONTEXT" context verify`. Read the relevant resource or team to establish access to that operation. `context version` reports the server version, which is separate from `coolify version`. 5. Resolve the resource through inventory and detail commands. Check its project, environment, server, and type before a mutation. Use returned resource UUIDs, not internal numeric IDs; team commands use numeric team IDs. ## Execute and verify - Honor the requested action and existing authorization. An authorized deployment or update does not need another confirmati