hetzbot-remove-service

Remove a first-party service from a single Hetzbot-managed host.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely remove a first-party service from a host, ensuring complete cleanup and state synchronization.

Core Features & Use Cases

  • Interactive, deterministic workflow to stop, remove, and decommission a service on a single host.
  • Backs up the service's Postgres data (optional) before removal.
  • Updates fleet state and triggers conditional reconfiguration (Caddy) on public hosts.

Quick Start

Provide the host name and service to remove, then confirm the prompts to execute the on-host removal.

Frequently Asked Questions about hetzbot-remove-service

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

FAQPage Schema
How do I safely remove a systemd service from a host without losing data?

To safely remove a systemd service from a host, you can use a deterministic workflow that optionally backs up Postgres data, stops and purges the service, cleans directories, removes the service user, and reconfigures Caddy.

What is the best way to decommission a service across a fleet-managed host?

The best way to decommission a service across a fleet-managed host involves a multi-step process that backs up data, purges the service, cleans on-host directories, removes users, and synchronizes the updated fleet state.

How does database cleanup work when removing a service from a host?

Database cleanup during service removal works by optionally backing up the service's Postgres data before stopping and purging the service, ensuring no critical data is lost during the decommissioning process.

Can I reconfigure Caddy automatically when removing a service from a public host?

Yes, you can reconfigure Caddy automatically when removing a service from a public host, as the decommissioning workflow triggers conditional Caddy reconfiguration alongside removing the service user and cleaning directories.

What steps are required to completely purge a service user and its directories from a host?

Completely purging a service user and its directories requires stopping the service, cleaning on-host directories, removing the dedicated service user, and syncing fleet state to maintain accurate host configuration.