ericrisco/rsc-harness / skills/coolify
coolify
FlaggedUse when self-hosting apps and databases with Coolify on a VPS you own — install, first-admin lockdown, Git-to-deploy (Nixpacks/Dockerfile/compose), managed Postgres/Redis, scheduled S3 backups, domains + auto-SSL. NOT a PaaS someone else runs (that is `railway`), NOT sizing/hardening the box (that is `hetzner`), NOT authoring Dockerfiles (that is `docker`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.1 KB |
| evals/README.md | markdown | 1.5 KB |
| evals/cases.yaml | config | 4.1 KB |
| references/databases-and-backups.md | markdown | 4.5 KB |
| references/deploy-recipes.md | markdown | 4.7 KB |
| references/install-and-proxy.md | markdown | 4.4 KB |
| scripts/verify.shexecutable | script | 5.2 KB |
evals/cases.yaml
View on GitHubskill: coolify
should_trigger:
- prompt: "Install Coolify on my fresh Ubuntu 24.04 VPS and deploy my app from a GitHub repo."
why: "Core install + Git deploy path: install one-liner as root, first-admin lockdown, build-pack + source wiring."
- prompt: "My Vercel bill exploded this month. I want to move everything onto a box I own and pay a flat rate instead. How do I set that up?"
why: "Non-obvious cost/sovereignty trigger — user never says Coolify, but 'box I own + flat rate' instead of a metered PaaS is exactly the own-the-box value prop."
- prompt: "Set up nightly Postgres backups to Cloudflare R2 for the database I run in Coolify."
why: "In-product scheduled backup to S3-compatible storage (R2) with cron — a named core capability, including the restore-drill rule."
- prompt: "Montar mi propio PaaS en un VPS barato con Coolify y desplegar varias apps con SSL automático."
why: "Spanish trigger; self-hosting your own PaaS on a cheap VPS with multiple apps and automatic SSL is squarely this skill."
- prompt: "Vull autoallotjar les meves apps amb Coolify i una base de dades gestionada al meu servidor."
why: "Catalan trigger; self-hosting apps + a managed database on your own server is the provision-and-connect core."
- prompt: "I already have a server running. I just want a self-hosted control plane to manage my deploys, env vars and SSL certs from one dashboard."
why: "Non-obvious 'control plane on my own server' phrasing — the box exists, the user wants the orchestration layer, which is precisely what Coolify is."
should_not_trigger:
- prompt: "Which Hetzner plan should I pick and how do I harden SSH and the firewall on the box itself?"
route_to: "hetzner"
why: "VPS hardware sizing + OS/SSH/firewall hardening is the box layer, not the control plane Coolify runs on."
- prompt: "Help me write a multi-stage Dockerfile and optimize my image layer caching."
route_to: "docker"
why: "Generic Docker image authoring — Coolify runs images but doesn't teach how to author/optimize them."
- prompt: "I just want a managed PaaS where I git push and they run it — I don't want to own or maintain any server."
route_to: "railway"
why: "Push-and-forget managed PaaS is the exact inverse of Coolify's own-the-box premise."
- prompt: "My Postgres query is doing a seq scan and is slow — which index should I add?"
route_to: "postgresdb"
why: "SQL/index/query tuning is engine-level work; Coolify only provisions and backs up the DB, it doesn't tune it."
- prompt: "Set up the A record and nameservers for my domain at the registrar."
route_to: "domains-dns"
why: "DNS records / registrar / propagation is the domains-dns layer; Coolify consumes the resolved hostname, it doesn't manage DNS."
capability:
- scenario: "Stand up Coolify on a fresh Ubuntu 24.04 VPS, deploy a Next.js app from a GitHub repo with a managed Postgres, and configure nightly backups to S3-compatible storage with a custom domain + automatic SSL."
must_include:
- "Runs the install one-liner (curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash) AS ROOT, noting non-root is not fully supported"
- "Calls out first-admin lockdown: register at http://<ip>:8000 immediately because the first account permanently owns the instance"
- "Gives the port/firewall matrix: 8000 (and 6001/6002) restricted to the operator, 80/443 public"
- "Picks a build pack (Nixpacks default) and connects the GitHub source with a branch"
- "Sets app secrets as Coolify env vars / secrets injected at runtime, never baked into the image or committed"
- "Provisions managed Postgres and connects the app over the INTERNAL Docker hostname, with the DB port NOT publicly exposed"
- "Ensures the database has a named volume so data survives recreate, and the service has a healthcheck"
- "Adds the custom domain and gets automatic Let's Encrypt SSL via the Traefik proxy on 80/443"
- "Configures the S3 backup destination + cron schedule + retention AND an explicit restore-test/drill step"
- "Acknowledges the boundary that VPS sizing/firewall/SSH hardening is hetzner/digitalocean, not this skill"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |