Uptime Kuma

Interact with Uptime Kuma monitoring server. Use for checking monitor status, adding/removing monitors, pausing/resuming checks, viewing heartbeat history. Triggers on mentions of Uptime Kuma, server monitoring, uptime checks, or service health monitoring.

This skill appears to do what it says: manage Uptime Kuma via its API. Before installing, note: (1) the skill requires UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, and UPTIME_KUMA_PASSWORD at runtime even though the registry metadata didn't declare them — you'll need to provide these credentials. (2) It asks you to pip install the uptime-kuma-api package; verify that package on PyPI and your environment before installing. (3) Provide a least-privilege or dedicated Uptime Kuma account if possible, and ensure the UPTIME_KUMA_URL points only to servers you control (e.g., localhost or a known internal URL). (4) The skill's source/homepage is not provided in the registry; if provenance is important, ask the publisher for a homepage or inspect the included kuma.py (provided) and the uptime-kuma-api package source before use.

Type: OpenClaw Skill Name: uptime-kuma Version: 1.0.0 The skill is designed to interact with an Uptime Kuma server and requires access to `UPTIME_KUMA_URL`, `UPTIME_KUMA_USERNAME`, and `UPTIME_KUMA_PASSWORD` environment variables, as explicitly stated in `SKILL.md` and accessed in `scripts/kuma.py`. While this credential access is necessary for the skill's stated purpose and there is no evidence of malicious intent (e.g., exfiltration to unauthorized endpoints), the handling of sensitive credentials, even for legitimate use, constitutes a high-risk capability that warrants a 'suspicious' classification rather than 'benign' in a security review.