agentleFS
Sign inStart free
abdullahkhawerabdullahkhawer/devops-skills/skills/hetzner-cli/SKILL.md

hetzner-cli

Skill8 starsChanged 6 months agoApache-2.0View on GitHub

Use the correct Hetzner Cloud CLI (hcloud) context when running Hetzner Cloud commands based on the target environment.

  • Installs packages

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When running hcloud commands, always pass the --context flag based on the target environment.

    line 8
  2. Very specific:

    Update the context map below with your hcloud CLI context names:

    line 12
  3. Distinctive:

    If not already authenticated, inform the user that setup is required and ask them to complete the following steps manually.

    line 21
  4. Very specific:

    Always specify --context explicitly — never rely on the active hcloud context, as it may point to the wrong project.

    line 79
  5. Distinctive:

    If the target environment is unclear, ask the user before running the command.

    line 80
  6. Distinctive:

    NEVER run any command in the "Never run" table above without explicit user instruction — a human must execute these, especially against …

    line 81
  7. Very specific:

    NEVER read or output the API token stored in hcloud CLI contexts or any credential value.

    line 82
  8. Very specific:

    If unsure which project a context belongs to, run hcloud --context <context> context active to verify before proceeding.

    line 83

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hetzner Cloud CLI Skill

When running hcloud commands, always pass the --context flag based on the target environment.

Configuration

Update the context map below with your hcloud CLI context names:

EnvironmentContext
Production<your-prod-context>
Staging / Non-Prod<your-nonprod-context>

Prerequisites (one-time setup by user)

If not already authenticated, inform the user that setup is required and ask them to complete the following steps manually. Do not perform these steps yourself.

brew install hcloud
hcloud context create <your-context-name>
hcloud context list

Command Format

hcloud --context <context> <resource> <command> [options]

Examples

# Production
hcloud --context <your-prod-context> server list

# Staging / Non-Prod
hcloud --context <your-nonprod-context> server list

Available Commands

Read-only (safe, no confirmation needed)

CommandDescription
server list / server describe <name>List or describe servers
volume list / volume describe <name>List or describe volumes
load-balancer list / load-balancer describe <name>List or describe load balancers
network list / network describe <name>List or describe networks
firewall list / firewall describe <name>List or describe firewalls
context list / context activeShow CLI context information

Mutating operations (confirm with user before running)

CommandDescription
server createCreate a new server
volume createCreate a new volume
load-balancer createCreate a new load balancer
server resizeResize a server

Never run — requires explicit human approval

CommandReason
server deleteIrreversible resource deletion
volume deleteIrreversibly deletes a volume and its data
load-balancer deleteIrreversibly deletes a load balancer
server reset / server poweroffDisrupts running workloads
firewall deleteRemoves network security controls

Rules

  • Always specify --context explicitly — never rely on the active hcloud context, as it may point to the wrong project.
  • If the target environment is unclear, ask the user before running the command.
  • NEVER run any command in the "Never run" table above without explicit user instruction — a human must execute these, especially against production.
  • NEVER read or output the API token stored in hcloud CLI contexts or any credential value.
  • If unsure which project a context belongs to, run hcloud --context <context> context active to verify before proceeding.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free