hetzbot-init-fleet

Scaffold a fleet repository with hosts.tfvars, services/, and setup scripts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold a new fleet repository that consumes hetzbot as a sibling clone, enabling rapid onboarding of new fleets.

Core Features & Use Cases

  • Generates a minimal fleet repository with hosts.tfvars, services/, .env.example, justfile, and README, ready to customize.
  • Provides a repeatable scaffold that can be re-used for testing or production fleets.
  • Useful for teams starting new fleets who want a consistent starting point and clear instructions.

Quick Start

Run the init-fleet skill to scaffold a new fleet repository at a chosen path.

Frequently Asked Questions about hetzbot-init-fleet

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

FAQPage Schema
How do I scaffold a new infrastructure fleet repository from a template?

Scaffolding a fleet repository generates a minimal structure with hosts.tfvars, services/, .env.example, justfile, and README. The process copies templates, substitutes placeholders, and runs idempotent setup scripts to create a ready-to-customize repo.

What files are included when bootstrapping a fresh fleet repository?

Bootstrapping a fleet repository includes hosts.tfvars for host configuration, a services/ directory, .env.example for environment variables, a justfile for task automation, and a README with setup instructions.

Do I need local filesystem access to set up a fleet scaffold?

Yes, setting up a fleet scaffold requires local filesystem access to copy templates, substitute placeholders, and run idempotent setup scripts including init-fleet.sh, setup-env.sh, and check-env.sh.

Can I reuse a fleet scaffold for testing and production environments?

Yes, the fleet scaffold is repeatable and can be re-used for both testing and production fleets. It provides a consistent starting point with clear instructions for teams onboarding new infrastructure environments.

What's the best way to automate onboarding for multiple fleet repositories?

The best way to automate fleet onboarding is using a repeatable scaffolding process that generates a minimal repository with standardized files like hosts.tfvars and a justfile, ensuring consistent setup across multiple fleets.

Why does the fleet scaffold reference hetzbot as a sibling clone?

The fleet scaffold references hetzbot as a sibling clone so the new fleet repository can consume hetzbot directly. This architecture enables rapid onboarding by keeping hetzbot alongside the fleet for integration.