beszel

What This Skill Does

The Beszel skill for OpenClaw provides a direct interface to monitor the health and performance of your home lab servers via the Beszel monitoring system, which is built on PocketBase. This integration allows users to query system-wide health metrics and container-specific resource utilization without needing to log into a web dashboard. By leveraging the command-line interface directly through the OpenClaw agent, you can maintain visibility over your infrastructure’s CPU, RAM, and container state, ensuring that your background services are running smoothly and within expected performance parameters.

Installation

To integrate the Beszel monitoring skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/karakuscem/beszel-check

Ensure that you have your local Beszel instance properly configured and that the necessary environment variables or path configurations for the Beszel script are present in your ~/.zshrc file as specified in the command patterns. Once installed, the skill will be automatically indexed by OpenClaw.

Use Cases

This skill is perfect for home lab enthusiasts and DevOps engineers who want to automate server oversight. You can use it to perform routine health checks on your primary Docker host, diagnose performance bottlenecks by listing high-CPU containers, or include system status reports as part of a daily diagnostic routine handled by the AI agent. It is particularly useful for users managing multi-node clusters where jumping between different dashboards is inefficient.

Example Prompts

1. "OpenClaw, can you run the beszel status command and tell me if any of my servers are offline?"
2. "Check my home lab; which containers are currently consuming the most CPU power?"
3. "Summarize the current state of my infrastructure using the beszel utility."

Tips & Limitations

• Permissions: Ensure the user running OpenClaw has the necessary read permissions to execute the local index.js script.
• Network: This skill requires network connectivity to your internal Beszel/PocketBase instance. If the service is behind a restrictive firewall, ensure local traffic is permitted.
• Scope: The current implementation provides a snapshot of data. It does not provide historical trend analysis or persistent logging; it is strictly a real-time status retrieval tool. If you need historical graphs, you must access the standard Beszel web UI.