Beszel

What This Skill Does

The Beszel skill provides an end-to-end management framework for the Beszel monitoring stack. It facilitates the deployment, configuration, and maintenance of Beszel hubs and Docker-based agents across self-hosted infrastructure. The skill automates the operational logic required to keep monitoring robust, including the management of persistent storage in ~/beszel/, tracking of node inventory, and iterative alert calibration. By enforcing architectural patterns and diagnostic sequences, the skill ensures that users maintain high visibility into their server health while minimizing alert fatigue.

Installation

To integrate this skill, use the OpenClaw command: clawhub install openclaw/skills/skills/ivangdavila/beszel. Upon first use, the skill will initialize your local working environment. It will request permission to create the ~/beszel/ directory, which acts as the source of truth for your monitoring topology, alert thresholds, and incident history. It is recommended to keep this directory synced or backed up as part of your system recovery plan.

Use Cases

• Initial Deployment: Designing a hub-and-spoke monitoring architecture suitable for your specific number of hosts and network topology.
• Agent Onboarding: Securely adding new Docker agents to an existing hub without compromising security or exposing sensitive credentials.
• Alert Tuning: Analyzing historical system metrics to refine thresholds, reducing false positives during maintenance windows or high-load business events.
• Incident Management: Following a structured diagnostic playbook to isolate connectivity issues, clock drift, or resource exhaustion across your monitored fleet.
• Version Upgrades: Executing rolling upgrades for hub and agents with verified backup and rollback procedures to ensure system stability.

Example Prompts

• "I'm planning to monitor 5 new VPS instances. Can you help me design the deployment topology and generate the necessary configuration steps?"
• "I am getting constant high CPU alerts for my database server during my scheduled backup window. How can I use the alert tuning workflow to calibrate this threshold?"
• "I need to upgrade my Beszel hub version. What is the recommended backup process and rollback plan before I start the migration?"

Tips & Limitations

To get the most out of Beszel, always establish a baseline metric period before setting strict alerts. Avoid the common trap of mass-enrolling agents before defining who receives notifications, as this often leads to alert fatigue. Note that the skill enforces a 'one-variable-at-a-time' troubleshooting approach to ensure that diagnostics are clear. Furthermore, remember that clock drift is a frequent silent killer of incident reporting; ensure all hosts are NTP-synced to prevent confusing log timelines. Never store sensitive SSH keys or API secrets directly in the ~/beszel/ notes; the skill is designed to manage configurations, not secrets management.