hetzbot-snapshot-host

Create on-demand Hetzner Cloud snapshots of a specific host.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/tomspiegl/hetzbot --skill hetzbot-snapshot-host
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hetzbot-snapshot-host
Source: https://github.com/tomspiegl/hetzbot/tree/main/skills/hetzner/snapshot-host
Command: npx skills add https://github.com/tomspiegl/hetzbot --skill hetzbot-snapshot-host

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually snapshotting Hetzner hosts is error-prone and time-consuming; this skill provides on-demand host-level images to enable safe rollbacks.

Core Features & Use Cases

  • Create manual snapshots of named Hetzner hosts with descriptive labels to capture a known-good state before risky changes.
  • Automatically validate host identity via tofu output, optionally quiesce services, and poll the snapshot action until completion.
  • Use cases include pre-upgrade rollbacks, disaster recovery planning, and testing infrastructure changes in a deterministic way (each snapshot is a reusable image).

Quick Start

Use the features to snapshot hetz-1 before a major upgrade.

Frequently Asked Questions about hetzbot-snapshot-host

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

FAQPage Schema
How do I create on-demand Hetzner Cloud snapshots for server rollback?

Create on-demand Hetzner Cloud snapshots by targeting a specific host's hcloud_id from tofu output, optionally quiescing services, and polling the create_image action until completion to capture a known-good state for rollback.

Do I need an HCLOUD_TOKEN to automate Hetzner host snapshots?

Yes, automating Hetzner host snapshots requires an HCLOUD_TOKEN to authenticate API requests, validate host identity via tofu output, and poll the create_image action until the snapshot completion.

Can I quiesce services before taking a Hetzner Cloud snapshot?

Yes, you can optionally quiesce services before taking a Hetzner Cloud snapshot to ensure data consistency, after which the skill polls the create_image action until completion to finalize the rollback image.

What is the best way to manage rollback snapshots across a fleet of Hetzner servers?

The best way to manage rollback snapshots across a fleet of Hetzner servers is using on-demand host-level images with descriptive labels, validating host identity via tofu output to ensure deterministic disaster recovery.