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.

Security Scan

The skill appears to do what it claims (HTTP uptime checks + optional webhook/email alerts) and contains only simple shell scripts; issues found are implementation inconsistencies/bugs rather than signs of misdirection or exfiltration.

Purpose & Capability

The name/description (uptime monitoring) matches the included scripts (check.sh, alert.sh, report.sh) and the only required binary is curl — this is proportionate. However the registry metadata declares no required environment variables while SKILL.md requires MONITOR_URLS (required) and optional ALERT_WEBHOOK_URL/ALERT_EMAIL; that mismatch is an oversight and should be corrected so users are aware of required configuration.

Instruction Scope

SKILL.md gives focused runtime instructions (run check.sh, alert.sh, report.sh). The scripts only read the environment variables documented in SKILL.md and write logs into a local logs directory. There is a small inconsistency: SKILL.md claims logs are written to ~/.openclaw/workspace/skills/uptime-monitor/logs/status.log, but the scripts write to a logs directory relative to the skill (scripts/../logs). No unexpected files, system-wide credentials, or external endpoints are referenced in code.

Install Mechanism

This is instruction-only with shell scripts included; there is no installer, package download, or external install URL. Risk from install mechanics is low. The only runtime dependency is curl (declared).

Credentials

The skill uses MONITOR_URLS, ALERT_WEBHOOK_URL and ALERT_EMAIL which are appropriate for its purpose. However the registry incorrectly lists no required env vars — MONITOR_URLS is effectively required at runtime. There are no hardcoded external secrets or unexpected credential requests.

Persistence & Privilege

always is false and the skill does not modify other skills or system configuration. It writes only to its own logs directory and sends outbound requests only to user-supplied webhook URLs.

Assessment

This skill is generally coherent for uptime monitoring, but review these points before installing: 1) You must set MONITOR_URLS (SKILL.md marks it required) even though registry metadata doesn't declare it — otherwise the scripts will fail. 2) Decide whether you want alerts to go to a webhook (ALERT_WEBHOOK_URL) or email (ALERT_EMAIL) and only provide trusted webhook URLs. 3) The scripts write logs to a logs directory next to the skill (scripts/../logs); confirm where that resolves in your agent filesystem and that permissions are acceptable. 4) There are minor bugs/behaviors to be aware of: check.sh enables set -e which can cause the script to exit early on curl failures (this may change how errors are logged/handled), and report.sh's date/grep logic for cutoff filtering looks fragile on different platforms. 5) Confirm availability of the mail command if you intend to use email alerts. If you want higher assurance, ask the publisher to (a) declare MONITOR_URLS in registry metadata, (b) clarify the intended log path, and (c) fix the error-handling/date logic in check.sh and report.sh.

Monitor HTTP endpoints and alert when services go down.

Environment Variables

Variable	Required	Default	Description
MONITOR_URLS	Yes	—	Comma-separated list of URLs to monitor
ALERT_WEBHOOK_URL	No	—	Webhook URL to send alerts (Discord, Slack, etc.)
CHECK_INTERVAL	No	60	Interval in seconds between checks
ALERT_EMAIL	No	—	Email address for alert notifications

Scripts

check.sh — HTTP Health Check

Performs HTTP check with response time measurement.

./scripts/check.sh <url>

Output:

OK|https://example.com|200|245ms
FAIL|https://example.com|000|timeout

Exit code: 0 = up, 1 = down

alert.sh — Send Alert

Sends alert via webhook or email when a service is down.

./scripts/alert.sh <url> <status_code> <response_time> <error_message>

report.sh — Uptime Report

Generates a daily uptime summary from the log file.

./scripts/report.sh

Output: Markdown-formatted report with uptime % per URL.

Usage Example

export MONITOR_URLS="https://example.com,https://api.example.com"
export ALERT_WEBHOOK_URL="https://discord.com/api/webhooks/..."
export CHECK_INTERVAL=60

# Run a single check
./scripts/check.sh https://example.com

# Generate report
./scripts/report.sh

Notes

• Uses curl with a 10-second timeout for checks
• Logs results to ~/.openclaw/workspace/skills/uptime-monitor/logs/status.log
• Alert webhook expects a JSON payload (compatible with Discord/Slack/PagerDuty)