Hetzner Cloud CLI

**Judgement:** A strong, safety-conscious skill for users who already use or want to use the official Hetzner Cloud CLI. It is well-suited to infrastructure and DevOps workflows where changes are mediated through explicit CLI commands rather than opaque automation. **What it does well:** - Guides installation and configuration of the `hcloud` CLI across major Linux distros and macOS. - Covers core Hetzner resources: servers, volumes, networks, firewalls, snapshots/images, SSH keys, and locations. - Enforces clear guardrails: no delete operations, no credential exposure, confirmation before create/modify, and snapshot recommendations before changes. - Encourages good practices such as context usage for multiple projects and structured outputs (JSON/YAML) for downstream tools. **Key risks / limitations:** - Still capable of proposing impactful create/modify commands (e.g., firewall or network changes) that can cause downtime or cost if a user approves them without understanding. - Assumes the user is the legitimate account owner; verification in group contexts relies on user honesty. - Requires the `hcloud` CLI to be installed and configured; without that, suggested commands won’t work, and troubleshooting may be non-trivial for beginners. - No delete operations are allowed, which improves safety but limits full lifecycle management (cleanup must be done manually outside the skill’s guidance). **Best-fit scenarios:** - Developers/DevOps engineers managing Hetzner Cloud who want help drafting safe CLI commands and following best practices around snapshots and contexts. - Users building scripts, CI/CD pipelines, or automation around `hcloud` and needing correct command patterns and output format options. - Situations where transparency and review of each infrastructure command are important, and users prefer explicit, copy-pastable CLI over fully automated changes.