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 is internally consistent with an uptime-monitoring purpose: it only needs curl, uses local scripts to check endpoints, send alerts to user-provided webhooks/email, and writes logs to a local logs directory.

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.

Assessment

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.

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)