Uptime Monitor Agent

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 implement a simple uptime monitor and alerting scripts, but metadata and runtime instructions are inconsistent (required environment variables are not declared) and the skill will send HTTP/webhook requests and write logs — review before use.

Purpose & Capability

The files and scripts match the stated purpose (HTTP checks, webhook/email alerts, reports). However the registry metadata declares no required environment variables while SKILL.md requires MONITOR_URLS (required) and optional webhook/email env vars; this mismatch is unexpected and reduces clarity about what secrets/config the skill needs.

Instruction Scope

Runtime instructions and scripts stay within uptime-monitoring scope: they perform curl checks, log results, post to a configured webhook, and send email via the system mail command. They do not read system credentials or arbitrary files. Note: SKILL.md claims logs are written to ~/.openclaw/... while scripts use a relative ../logs path — benign but inconsistent.

Install Mechanism

There is no installer and no downloads; this is an instruction-only skill with bundled shell scripts. Nothing is pulled from external URLs during install, which is a lower-risk pattern.

Credentials

The skill requires configuration via environment variables (MONITOR_URLS required, ALERT_WEBHOOK_URL, ALERT_EMAIL optional), but the registry metadata lists no required env vars. Because env vars are not declared, an automated install may not surface these requirements. The webhook/email functionality will transmit monitoring data to endpoints provided by the user; ensure any webhook URL is trusted. No unrelated credentials are requested.

Persistence & Privilege

The skill does not request permanent 'always' inclusion and does not modify other skills or system-wide configs. It writes logs to a local logs directory under the skill and may invoke outbound network requests when alerts are triggered (expected behavior for a monitor).

What to consider before installing

This skill's code matches an uptime monitor, but the metadata is incomplete — MONITOR_URLS is required at runtime though not declared in the registry. Before installing: (1) verify and set MONITOR_URLS and any ALERT_WEBHOOK_URL to trusted endpoints (a webhook will receive JSON payloads); (2) review the scripts locally (they use curl and may call mail) and confirm you are comfortable with outbound HTTP posts and writing logs to the skill's logs directory; (3) ensure the environment has curl and an MTA if you rely on email alerts; (4) consider running in an isolated environment if you want to limit network exposure; and (5) ask the publisher to correct the registry metadata so required env vars are declared. If you need higher assurance, request provenance (homepage/source) or a signed release.

Uptime Monitor

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)