← ClaudeAtlas

coolify-managerlisted

Manage and troubleshoot Coolify deployments using the official CLI (v1.4.0) and API. Use this skill when the user needs help with Coolify server management, WordPress troubleshooting on Coolify, debugging service issues, checking SSL certificates, accessing containers, managing applications and databases, deploying code, creating services or databases, managing environment variables, configuring backups with S3 and retention policies, or performing any deployment operations through Coolify. Also use when the user mentions docker containers on Coolify, deploy failures, self-hosted infrastructure management, or needs to batch-deploy multiple resources at once. Particularly useful for diagnosing down services, fixing .htaccess issues, REST API problems, and managing one-click services like WordPress, Ghost, n8n, Supabase, Uptime Kuma.
AIBiz-Automatyzacje/claude-cron · ★ 1 · DevOps & Infrastructure · score 64
Install: claude install-skill AIBiz-Automatyzacje/claude-cron
# Coolify Manager Skill for managing Coolify deployments through CLI (v1.4.0) and direct API access. Covers diagnosing issues, fixing WordPress problems, managing containers, creating resources, and performing deployments. ## Prerequisites 1. Coolify instance access (self-hosted or cloud) 2. API token from Coolify dashboard at `/security/api-tokens` 3. Coolify CLI installed (see `scripts/install_coolify_cli.sh`) ## Setup ```bash # Install CLI bash scripts/install_coolify_cli.sh # Add context coolify context add <name> <url> <token> # Verify connection coolify context verify # Quick health check bash scripts/check_health.sh ``` For full CLI reference including all flags and subcommands, load `references/cli_commands.md`. ## Diagnosing Issues — Decision Tree When a user reports a problem, follow this tree: ### 1. Service Availability ``` Site is down? ├── Check status: coolify resource list ├── Get details: coolify service get <uuid> ├── Check logs: coolify app logs <uuid> --follow │ └── Logs point to config issue? → Check env vars, restart │ └── Logs point to crash? → Check app code, memory limits └── Restart: coolify service restart <uuid> ``` ### 2. WordPress-Specific ``` WordPress issue? ├── 500 error after .htaccess change → Load references/wordpress_fixes.md ├── REST API warnings in Site Health → Likely false positive, test with curl ├── PHP limits (upload, memory, etc.) → Fix via .htaccess php_value directives ├── SSL certificate issues → Check wi