hetzner-cloud-ops

Inspects Hetzner Cloud provisioning signals and writes an infrastructure operations plan.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill hetzner-cloud-ops-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hetzner-cloud-ops
Source: https://github.com/gmackie/agent-skills/tree/main/skills/hetzner-cloud-ops
Command: npx skills add https://github.com/gmackie/agent-skills --skill hetzner-cloud-ops-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, jq, ripgrep, and includes scripts (resource) and references (resource) components.

What problem does it solve? Teams running workloads on Hetzner Cloud often lack visibility into how servers are provisioned, bootstrapped, and networked, leading to drift between declared infrastructure and actual service setup. This Skill inventories the Hetzner surface in a repository and produces a concrete operations plan instead of treating Hetzner as an opaque VPS host. ## Core Features & Use Cases - Surface Inventory: Runs a helper script to detect hcloud CLI usage, Terraform provider configuration, cloud-init or user-data files, and bootstrap markers like Docker Compose, Caddy, or Traefik. - Provisioning and Drift Review: Evaluates whether server creation is reproducible, whether networking and firewall assumptions are explicit, and where docs and bootstrap scripts disagree. - Ops Plan Generation: Writes a dated operations plan under docs/infrastructure/ covering the provisioning model, bootstrap and networking review, drift risks, and next steps. - Use Case: Before migrating services to a new Hetzner project, run the inventory to confirm Terraform manages all servers and that cloud-init is actually wired into provisioning, then capture the gaps in a reviewable plan. ## Quick Start Ask the agent to review this repository's Hetzner Cloud setup and produce an operations plan covering provisioning, bootstrap, networking, and drift risks.

Frequently Asked Questions about hetzner-cloud-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Hetzner Cloud infrastructure in a repository?▼

Run the inspect-hetzner-surface.sh script with --repo pointing at the project root. It scans for hcloud CLI usage, Terraform hcloud provider blocks, cloud-init or user-data files, and bootstrap markers like Docker Compose, Caddy, or Traefik, then reports results as text or JSON.

How to detect drift between Terraform and actual Hetzner server setup?▼

The Skill reviews whether server creation is reproducible through Terraform or the hcloud CLI versus ad hoc dashboard work, and flags cases where cloud-init exists but is unused, servers are hand-configured, or repo docs and bootstrap scripts disagree.

Does this work with Terraform-managed Hetzner projects?▼

Yes, the inventory script explicitly searches for the Terraform hcloud provider and related resources like floating IPs and firewalls. The review then checks whether Terraform-based provisioning and bootstrap are reproducible and whether networking assumptions are visible.

What tools are required to run the Hetzner surface inspection?▼

The helper script requires bash, jq, and ripgrep (rg) to be installed. It takes a --repo path argument and an optional --format flag accepting text or json output.

When should I not use this Skill for server debugging?▼

This Skill is scoped to Hetzner Cloud operations planning, not generic Linux debugging. If the task is troubleshooting a running service or OS-level issue unrelated to provisioning, bootstrap, or infrastructure drift, use a general debugging approach instead.