Skill · AI & Development

Docker & Coolify Self-Hosting Runbook

Docker & Coolify Self-Hosting Runbook is a Claude skill for AI & Development. Turns your self-hosted Docker and Coolify stack into a written runbook: a readiness score out of 20, a server baseline, a safe Coolify setup, backups with a restore drill, and an outside-in triage ladder for outages. It costs $8.99 on Agensi. It runs on any Claude plan, including Free. Part of the StrategistKit catalog of 190+ focused Claude skills.

Category
AI & Development
Deliverable
1 .skill bundle
Outputs
6
Last updated
19 Oct 2026
$8.99 One-time · lifetime updates
Become a member to fetch

10 credits — included with a membership (30 credits/mo).

Prefer a one-time purchase, without joining?

Buy once on Agensi (opens in a new tab)

StrategistKit Affiliate. One-time purchase on Agensi. Payment, delivery and refunds are handled by the marketplace — see their policy for refund terms.

  • Works in Claude Free, Pro, Max, Team and Enterprise
  • Lifetime access to updates
  • One-time purchase on Agensi. Payment, delivery and refunds are handled by the marketplace — see their policy for refund terms.
Or get a free skill every month. Subscribers get one curated skill, free, every 1st. Pick yours →

Overview

What Docker & Coolify Self-Hosting Runbook does.

Docker & Coolify Self-Hosting Runbook writes an operations runbook for apps you run with Docker and Coolify on your own VPS. It gives the exact command for each step, marks every command that deletes, overwrites or restarts, and marks its own assumptions as (assumed) so you can correct them.

A realistic input: "My Coolify app returns 502 right after a redeploy. Ubuntu 22.04, 4 GB RAM, Next.js + Postgres." Because this is an incident, the triage ladder comes first, filled in for the symptom, followed by the fastest safe recovery, the readiness table and the remaining sections in short form.

A sample triage step: the proxy returns 502, so the ladder tests the app from the proxy's side of the network with docker exec coolify-proxy wget. "Connection refused" points to the wrong port or an app that is not listening on all interfaces — for a standalone Next.js server.js, the fix is HOSTNAME=0.0.0.0.

Who it's for

Solo developers and small agencies who self-host apps, databases or WordPress sites with Docker and Coolify on a VPS they manage themselves.

What you get

One skill. 6 outputs.

One .skill bundle. Run it on your material and it returns:

01

Readiness score out of 20 across 10 controls, plus the top three actions ranked by risk reduced per hour spent

02

Server baseline: SSH keys only, provider firewall, automatic security updates, swap and Docker log rotation

03

Coolify install and lock-down: domain with HTTPS, ports 8000/6001/6002 closed, two-factor login, APP_KEY saved off the server

04

Deploy checklist per app: health check, secrets, persistent volumes, pinned database versions, memory limits and rollback

05

Backup table, PostgreSQL and MySQL/MariaDB dump and restore commands, and a 30-minute restore drill

06

7-rung outside-in triage ladder: outside check, DNS, TLS, proxy, app container, dependencies, host

How it works

Three steps. About two minutes.

Install

Add the .skill file to your Claude app. About 10 seconds.

Run it on your work

Invoke the skill and paste in your material.

Apply the output

Review, keep what works, and use it.

In depth

Why a Claude skill beats a prompt template.

A copy-paste prompt runs one static pass and stops. A skill is a bundled program — instructions, examples, and a workflow Claude runs as a unit: it asks for the right input, applies the same pattern every time, and returns the structured outputs above.

FAQ

Common questions.

What do I need to provide?

Nothing to start: with no details it builds the full runbook for a demo stack and says so. For a tailored version, give what runs on the server, the provider, OS and size, where backups can go off the server, how much downtime and data loss you can accept, and your Docker Engine version.

Does it help with an outage that is happening now?

Yes. If you describe an outage, an error code, a full disk or an out-of-memory problem, it puts the triage ladder and the fastest safe recovery first, including any backup that must happen before a fix, and gives the rest in short form.

Are the commands safe to paste?

Commands that delete, overwrite or restart are marked ⚠ changes state and come after the check that proves they are needed. Disk space is freed in a fixed order starting with the build cache, and volumes are never bulk-removed before an off-server backup is verified.

Does it cover Kubernetes or managed hosting?

No. It is for a VPS where you have a shell. Kubernetes clusters and managed PaaS hosting without shell access on the server are out of scope.

Which databases does it handle?

PostgreSQL, MySQL and MariaDB, with dump, restore-test and readiness-check commands for each, plus archives of named Docker volumes for uploads and files.

More in AI & Development

Skills used with this one.

Part of these collections