← Back to Skills Marketplace
kryzl19

Uptime Monitor

by KRYZL19 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
112
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install service-health-checker
Description
Monitor uptime of websites/services and alert when down. Use when checking if a website is reachable, monitoring service health, or getting alerted on downtime.
Usage Guidance
This skill appears to do only uptime checks and send alerts to destinations you provide, but review these points before installing: - Provide only trusted webhook URLs. The alert script will POST JSON to whatever ALERT_WEBHOOK_URL you set; do not point it at unknown or third-party endpoints you don't control. - The skill expects environment variables (MONITOR_URLS, ALERT_WEBHOOK_URL, ALERT_EMAIL, CHECK_INTERVAL) documented in SKILL.md but not declared in the registry metadata — make sure you set them intentionally. - Logs are written to the skill's logs directory (scripts use a relative ./../logs path which maps to the skill workspace). Logs contain monitored URLs, timestamps, and alert entries; if URLs are sensitive, protect that directory and its backups. - alert.sh can attempt to send email via the local mail command (may fail if mail is not available); it does not exfiltrate other system data. - If you want extra assurance, run the scripts in a sandboxed environment (or inspect/modify the scripts) and test with non-production/example URLs and a webhook you control. Overall: coherent with its stated purpose; the main issues are the missing env-var declarations in the manifest and the usual caution around webhook endpoints and log handling.
Capability Analysis
Type: OpenClaw Skill Name: service-health-checker Version: 1.0.0 The skill provides legitimate uptime monitoring and alerting functionality but contains critical shell injection vulnerabilities in `scripts/check.sh` and `scripts/alert.sh`. Specifically, these scripts pass unsanitized variables such as `$URL` and `$ALERT_EMAIL` directly into shell commands within double quotes, which allows for arbitrary command execution via command substitution (e.g., `$(...)`). While the behavior aligns with the stated purpose and no evidence of intentional malice was found, these implementation flaws pose a high risk of remote code execution.
Capability Assessment
Purpose & Capability
Name/description match the included scripts and required binary (curl). Minor inconsistency: the registry metadata lists no required environment variables, but SKILL.md and the scripts expect several env vars (MONITOR_URLS, ALERT_WEBHOOK_URL, ALERT_EMAIL, CHECK_INTERVAL). These environment variables are appropriate for the described purpose but should have been declared in the manifest.
Instruction Scope
SKILL.md instructs only to run the included scripts for health checks, alerts, and reports. The scripts operate on user-provided URLs and a user-provided webhook/email and write/read logs from the skill's logs directory. There are no instructions to read unrelated system files or to transmit data to hard-coded external endpoints.
Install Mechanism
No install spec (instruction-only skill with bundled scripts). This is the lowest-risk pattern; nothing is downloaded or written beyond the provided scripts.
Credentials
The scripts use a small set of environment variables (MONITOR_URLS, ALERT_WEBHOOK_URL, ALERT_EMAIL, CHECK_INTERVAL). Those are proportionate to monitoring/alerting. However, the registry manifest did not declare these env vars — the mismatch means the skill's required secrets/configuration are not captured in the manifest and users/tools may not surface the need to supply them.
Persistence & Privilege
Skill is not always-enabled, does not request elevated privileges, and does not modify other skills or global agent configuration. It reads/writes only its own logs directory under the skill workspace.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install service-health-checker
  3. After installation, invoke the skill by name or use /service-health-checker
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of uptime-monitor, a website/service uptime checker with alerting. - Monitors URLs and sends alerts via webhook or email when services are down. - Includes scripts for health checks, sending alerts, and generating daily uptime reports. - Configurable via environment variables for URLs, check interval, and notification settings. - Uses curl for HTTP checks and logs status/results for reporting. - Supports Markdown-formatted uptime summaries and alerting compatible with Discord/Slack/PagerDuty.
Metadata
Slug service-health-checker
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Uptime Monitor?

Monitor uptime of websites/services and alert when down. Use when checking if a website is reachable, monitoring service health, or getting alerted on downtime. It is an AI Agent Skill for Claude Code / OpenClaw, with 112 downloads so far.

How do I install Uptime Monitor?

Run "/install service-health-checker" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Uptime Monitor free?

Yes, Uptime Monitor is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Uptime Monitor support?

Uptime Monitor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Uptime Monitor?

It is built and maintained by KRYZL19 (@kryzl19); the current version is v1.0.0.

💬 Comments