Agent skill · software engineering · laguagu
hetzner-cloud
Manage Hetzner Cloud infrastructure with the `hcloud` CLI — servers, networks, firewalls, load balancers, volumes, DNS zones, SSH keys, primary/floating IPs, snapshots, certificates, placement groups, storage boxes. Use whenever the user mentions Hetzner, hcloud, VPS provisioning, or Hetzner location codes (fsn1, hel1, nbg1, ash, hil, sin) — even if they don't say "hcloud". CLI-only; does NOT cover Hetzner Robot (dedicated servers, separate product and API).
Why this skill is useful
Provides specific commands and workflows for managing Hetzner Cloud infrastructure that the AI wouldn't reliably generate on its own.
What it needs
Requires hcloud installed locally. Requires hetzner account access. About 4k tokens when loaded. Last updated 2026-08-03. 58 stars on the source repository.
What this skill does
Hetzner Cloud Operate Hetzner Cloud through the hcloud CLI. When in doubt about server types, prices, locations, images, or flag syntax, run the discovery command rather than rely on this file or pretraining — the CLI is current. Authenticate Generate a token in Hetzner Console → project → Security → API Tokens, then either: hcloud context create is the one common case that still prompts even with the env var set — pass --token-from-env to skip the prompt in non-interactive sessions. Health check: hcloud datacenter list. Mental model hcloud manages everything inside Hetzner Cloud: servers, networks, firewalls, load balancers, volumes, DNS zones, SSH keys, primary/floating IPs, snapshots, certificates, placement groups, storage boxes. It does not manage: Hetzner Robot — dedicated/auction servers, separate product and API. Project creation, billing, team membership, API token issuing — web console only. Discovery beats memorization. Pretraining ages; the CLI is current. Question Command --- --- Server types and prices hcloud server-type list Locations and datacenters hcloud location list OS images hcloud image list --type system (add --architecture arm for ARM) Command/flag details hcloud <resource> <verb> --help Everything in this project at a glance hcloud all list Is a server actually reachable? hcloud server describe <srv> -o json → publicnet.ipv4.blocked (see gotcha 9) Structured output for scripts: --output json jq …, --output columns=id,name,status, --output format='{{.PublicNet.IPv4.IP}}'. Workflows where order matters Single commands are well-covered by --help. The chains worth pinning down: Server with SSH key + firewall, ready to log in — key and firewall must exist before server create references them: Replace firewall rules atomically (don't drift via repeated add-rule): Gotchas 1. Public IPs get recycled. A new server may inherit a previously-used IP and SSH refuses with REMOTE HOST IDENTIFICATION HAS CHANGED!. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills laguagu/hetzner-cloud