← Back to Skills Marketplace
Server Health
by
muslimalfatih
· GitHub ↗
· v1.0.0
3533
Downloads
1
Stars
15
Active Installs
1
Versions
Install in OpenClaw
/install server-health
Description
Comprehensive server health monitoring showing system stats, top processes, OpenClaw gateway status, and running services. Perfect for quick health checks via Telegram or CLI.
Usage Guidance
What to consider before installing/running:
- Inspect the script yourself before running. It is a local shell script (no download/install), so running it executes whatever is in server-health.sh.
- The script reads /root/.openclaw/openclaw.json, session files under /root/.openclaw, and /usr/lib/node_modules/openclaw/package.json and calls the openclaw CLI. Those files can contain sensitive configuration or state; do not run it as root on production machines unless you trust the source.
- The skill metadata declares no dependencies, but the script expects jq, systemctl, docker (optional), and the openclaw CLI; ensure those are available and understand that openclaw status output may include internal details.
- The README mentions Telegram integration but there is no code for Telegram — do not assume remote forwarding or alerts are implemented. If you need alerts via Telegram, require an explicit, reviewed integration.
- If you want to use this: run it in a safe/test environment first, or run with least privilege (non-root) and verify what files are accessed (e.g., run under strace or in a container). If you need confirmation about what exactly openclaw status prints on your system, run that command separately to see what data could be exposed.
Capability Analysis
Type: OpenClaw Skill
Name: server-health
Version: 1.0.0
The skill bundle provides a server health monitoring script. While the script accesses sensitive paths like `/root/.openclaw/openclaw.json` and `/root/.openclaw/agents/main/sessions/*.json`, this access is directly aligned with its stated purpose of monitoring the OpenClaw gateway's status, configuration, and sessions. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts in the `SKILL.md` or `README.md` files. All commands used are standard system utilities for gathering health metrics, and the script only reads OpenClaw-specific files relevant to its monitoring function.
Capability Assessment
Purpose & Capability
The name/description claim a server health monitor (including OpenClaw gateway status), which aligns with the code's purpose. However the registry metadata and skill requirements declare no dependencies or privileges, while the script actually expects/uses jq, systemctl, docker, and the openclaw CLI and reads files under /root/.openclaw and /usr/lib/node_modules/openclaw. The README mentions Telegram use but there is no Telegram integration in the files. These mismatches (undeclared runtime dependencies, implied need for elevated access, and an advertised Telegram capability that isn't implemented) are inconsistent with the declared metadata.
Instruction Scope
The SKILL.md points to running server-health.sh; the script reads system state (top, ps, df, free, uptime), invokes systemctl and docker, runs pgrep/openclaw status, and directly reads /root/.openclaw/openclaw.json and session files (/root/.openclaw/agents/main/sessions/*.json) and /usr/lib/node_modules/openclaw/package.json. Reading OpenClaw config and session files can expose sensitive local configuration or session metadata. The instructions don't warn that root privileges may be required nor describe what sensitive files are read.
Install Mechanism
This is an instruction-only skill with no install spec (no network downloads or new binaries written by the skill). That is lower risk from an installation standpoint. The only risk is running the provided shell script itself (local code execution).
Credentials
The skill declares no required environment variables or credentials, yet the script accesses potentially sensitive files under /root/.openclaw and invokes the openclaw CLI which may surface internal configuration (models, ports, possibly tokens depending on configuration). It also reads package.json from a system path. Requesting zero credentials is not inconsistent by itself, but reading root-owned config without declaring privilege requirements is disproportionate and should be explicit.
Persistence & Privilege
The skill does not request persistent presence (always: false) and does not modify other skills or system-wide configuration. It only reads local system state and prints it; it does not attempt to write or persist credentials or enable itself automatically.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install server-health - After installation, invoke the skill by name or use
/server-health - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: System stats, OpenClaw Gateway status, and services monitoring
Metadata
Frequently Asked Questions
What is Server Health?
Comprehensive server health monitoring showing system stats, top processes, OpenClaw gateway status, and running services. Perfect for quick health checks via Telegram or CLI. It is an AI Agent Skill for Claude Code / OpenClaw, with 3533 downloads so far.
How do I install Server Health?
Run "/install server-health" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Server Health free?
Yes, Server Health is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Server Health support?
Server Health is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Server Health?
It is built and maintained by muslimalfatih (@muslimalfatih); the current version is v1.0.0.
More Skills