Skip to main content
Agent skill

Hetzner

Run hcloud CLI commands from the sandbox to inspect or change Hetzner Cloud resources — servers, volumes, networks, firewalls, load balancers, floating IPs, and images. Includes a setup script for selected Nuphos-bound Hetzner accounts.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Hetzner when an AI agent needs a reusable SKILL.md workflow for this job: Run hcloud CLI commands from the sandbox to inspect or change Hetzner Cloud resources — servers, volumes, networks, firewalls, load balancers, floating IPs, and images. Includes a setup script for selected Nuphos-bound Hetzner accounts.

When not to use it

Skip Hetzner when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/hetzner
# Save SKILL.md to ~/.claude/skills/hetzner/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/hetzner/SKILL.md. For a shared project, commit the folder at .claude/skills/hetzner/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Hetzner skill for this task: Use Hetzner when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Hetzner Cloud CLI

## Session isolation

Keep CLI credentials and settings inside the current session's `HOME` (`NUPHOS_SESSION_HOME`) and respect the supplied CLI config environment variables. Do not copy another session's or the runtime owner's credentials. Without `NUPHOS_SESSION_HOME`, CLI defaults may use shared runtime configuration; be aware of the affected scope.

Changing runtime-global settings is possible, but strongly discouraged unless the user understands the impact on other sessions and explicitly requests it. Explain the shared scope first; do not unset session isolation variables, write to the runtime owner's home, use a shared OS credential store, or modify shared shell startup files as routine setup. This is configuration isolation, not an OS security boundary.

Use this skill when the user wants to inspect or change Hetzner Cloud resources directly with `hcloud`, including servers, volumes, networks, firewalls, load balancers, floating IPs, SSH keys, and images.

Hetzner Cloud has no managed Kubernetes offering (there is no LKE/GKE/EKS equivalent), so there are no managed clusters or kubeconfigs to fetch here. If a user runs Kubernetes on Hetzner, it is self-managed on their servers — inspect it with `kubectl` using a kubeconfig they provide, not through this skill.

`hcloud` is provided by the runtime image's tool manifest, not baked into it: the first call downloads the pinned, checksum-verified release and can take a while, so let it finish rather than interrupt it. `nuphos-tools list` shows the tool and its state. If the command is missing entirely, or that install keeps failing, report the runtime mismatch instead of installing another build during the task; do not conclude that Nuphos lacks Hetzner credentials.

## Prefer Nuphos API for first-party reads

For read-only data Nuphos already exposes, call the Nuphos API first. This list route wraps its result in an object, so extract the array before piping to a `jq` filter (e.g. `.servers[]`, not `.[]`):

```bash ac /teams/<teamId>/hetzner-accounts # -> { "accounts": [...] } ac /teams/<teamId>/hetzner-accounts/<accountId>/servers # -> { "servers": [...] }

# list servers as id + name + status + location: ac /teams/<teamId>/hetzner-accounts/<accountId>/servers \ | jq -r '.servers[] | "\(.id)\t\(.name)\t\(.status)\t\(.location)"' ```

Use `hcloud` for details or operations not covered by that route.

## Setup

Authenticate before any `hcloud` call:

```bash bash skills/hetzner/scripts/setup-credentials.sh <teamId> <accountId> ```

The setup script uses the selected account for this agent session when `NUPHOS_SESSION_ID` is present, writes `~/.config/hcloud/cli.toml` with an active context, and also writes `~/.hetzner/nuphos.env` exporting `HCLOUD_TOKEN` for tools that read it from the environment. `hcloud` prefers `HCLOUD_TOKEN` when it is set, so `source ~/.hetzner/nuphos.env` if a later shell doesn't pick up the context.

Confirm the token works before mutating anything:

```bash hcloud server list -o json ```

## Common operations

```bash hcloud server list -o json hcloud server describe <server-id-or-name> -o json hcloud volume list -o json hcloud network list -o json hcloud firewall list -o json hcloud load-balancer list -o json hcloud floating-ip list -o json hcloud image list -o json ```

If `hcloud` returns auth errors, re-run the setup script before asking the user for a token.

## Safety

- Read-only by default. `list` and `describe` are safe. - Confirm with the user before mutations such as create, delete, poweroff, reboot, rebuild, resize (`change-type`), attach, detach, enable-protection, or disable-protection. - Do not print the Hetzner token, `cat ~/.config/hcloud/cli.toml`, or echo `HCLOUD_TOKEN`. - If a requested Hetzner account is not listed in the enabled credentials prompt, ask the user to update this session's credential selection.

Intended uses

  • Use Hetzner when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.