hetzbot-verify-fleet

Verify fleet health across hosts via SSH, containers, restic backups, and Postgres.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-setup, operators need confidence that the Hetzbot fleet is healthy and recoverable. This skill performs end-to-end fleet health verification across hosts, services, and infrastructure, validating that the deployment is functioning as intended and that any issues are surfaced early.

Core Features & Use Cases

  • End-to-end fleet health checks across tofu state, backups, containers, services, and external credentials.
  • Per-host and fleet-level validations that reveal recoverability issues after scaling or outages.
  • Use Case: After adding a host or service, run this verification to confirm all subsystems are healthy and ready for operation.

Quick Start

Run the verify.sh script on each fleet host to start end-to-end verification.

Frequently Asked Questions about hetzbot-verify-fleet

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

FAQPage Schema
How do I automate fleet health verification after infrastructure deployment?▼

Fleet health verification is automated by running a script on each host that checks tofu state, container status, services, Postgres, and Google API credentials across the entire fleet.

What does end-to-end fleet verification check after adding a new host?▼

End-to-end fleet verification validates tofu state, restic backups, container status, database readiness, timers, and Google API credential health to ensure the new host is fully operational and recoverable.

Can I check Postgres database readiness and restic backups via SSH?▼

Yes, cross-host fleet verification uses SSH to check Postgres database readiness, restic backups, container status, and timers across all deployed hosts.

When should I run a fleet health check on my infrastructure?▼

You should run a fleet health check after deploying or updating a fleet, or after adding a new host or service, to confirm all subsystems are healthy and surface any recoverability issues early.

Does fleet verification validate Google API credentials across all hosts?▼

Yes, fleet verification includes checking Google API credential health alongside tofu state and restic backups to ensure external service dependencies are functioning correctly.