← Back to Skills Marketplace
charlie-morrison

Site Health Monitor

by charlie-morrison · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
122
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install site-health-monitor
Description
Monitor websites for uptime, SSL certificate expiry, response time, HTTP errors, and content changes. Generate health reports and send alerts when issues are...
README (SKILL.md)

Site Health Monitor

Monitor one or more websites for health issues. Detect downtime, expiring SSL certs, slow responses, and content changes — then report or alert.

Quick Check (Single URL)

When user asks to check a single URL right now:

  1. Run scripts/check_site.sh \x3Curl>
  2. Parse the JSON output
  3. Present a formatted health report

Monitored Sites Config

For ongoing monitoring, maintain a config at user's chosen location (default: ~/.openclaw/workspace/site-monitor.json):

{
  "sites": [
    {
      "url": "https://example.com",
      "name": "Main Site",
      "checks": ["uptime", "ssl", "response_time", "content"],
      "alert_threshold_ms": 3000,
      "ssl_warn_days": 14,
      "content_selector": "title"
    }
  ],
  "defaults": {
    "checks": ["uptime", "ssl", "response_time"],
    "alert_threshold_ms": 5000,
    "ssl_warn_days": 30
  }
}

Health Checks

1. Uptime

  • HTTP GET to URL
  • Pass: 2xx/3xx status
  • Warning: 4xx status
  • Fail: 5xx, connection refused, timeout (>10s)

2. SSL Certificate

  • Run scripts/check_ssl.sh \x3Cdomain>
  • Pass: Valid, >30 days to expiry
  • Warning: \x3C30 days to expiry (configurable)
  • Fail: Expired, self-signed, or missing

3. Response Time

  • Measure TTFB + transfer via scripts/check_site.sh
  • Pass: Under threshold (default 5000ms)
  • Warning: 1-2x threshold
  • Fail: >2x threshold or timeout

4. Content Changes (Planned)

  • Fetch page, extract text, hash it
  • Compare against stored hash
  • Report if content changed since last check
  • Note: This feature is planned for v1.1

Reports

Single Site

## 🟢 example.com — Healthy
| Check         | Status | Detail                    |
|---------------|--------|---------------------------|
| Uptime        | ✅ UP  | 200 OK (143ms)            |
| SSL           | ✅ OK  | Expires in 87 days        |
| Response Time | ✅ OK  | 342ms (threshold: 5000ms) |
| Content       | — Same | No changes detected       |

Multi-Site Summary

## Site Health — 2026-03-26
| Site       | Status | Issues         |
|------------|--------|----------------|
| example.com| 🟢 OK | —              |
| api.foo.io | 🟡 WARN| SSL: 12 days  |
| shop.bar   | 🔴 DOWN| 503 error     |

Alerts

Alert when: site DOWN, SSL within warning window, response >2x threshold, 2+ consecutive failures.

Format: ⚠️ [site] — [issue]. [detail]. Checked at [time].

Scheduled Monitoring

Suggest cron job for recurring checks (30-60 min interval for production). Store last 100 results per site in ~/.openclaw/workspace/.site-monitor-history.json.

Scripts

  • scripts/check_site.sh \x3Curl> — HTTP health check, outputs JSON (status, timing, headers)
  • scripts/check_ssl.sh \x3Cdomain> — SSL cert check, outputs JSON (issuer, expiry, days remaining)
Usage Guidance
This skill appears to do what it claims, but review and prepare before installing: 1) The package metadata omits required binaries — ensure your environment has curl, openssl, python3 (and standard Unix utilities like mktemp, grep, sed). 2) The scripts use GNU-style date parsing; macOS (BSD date) may fail — test on your platform. 3) Alerts are referenced but no delivery method (webhook/email/Slack) is implemented — you will need to add an alerting integration if you want notifications. 4) The scripts will connect to the target sites and store monitoring data under ~/.openclaw/workspace — review that path and the scripts' output before running, and consider running them on a sandbox or non-production account first. 5) As with any code from an unknown source, inspect the scripts (they are short and readable) and run them with non-privileged user permissions.
Capability Analysis
Type: OpenClaw Skill Name: site-health-monitor Version: 1.0.0 The skill bundle is a legitimate website monitoring tool that uses bash scripts (scripts/check_site.sh and scripts/check_ssl.sh) to perform uptime and SSL certificate checks. The scripts use standard utilities like curl and openssl to gather metrics and provide structured JSON output for the agent to process. No evidence of data exfiltration, malicious persistence, or harmful prompt injection was found; the instructions in SKILL.md are consistent with the stated purpose of site health auditing.
Capability Assessment
Purpose & Capability
The name/description align with the provided scripts: check_site.sh (HTTP/timing) and check_ssl.sh (openssl certificate checks). However the registry metadata lists no required binaries while the scripts rely on curl, openssl, python3 (for JSON parsing), mktemp, and typical GNU date features — this mismatch is an omission that should be fixed before use.
Instruction Scope
SKILL.md stays within scope: it runs the included scripts, stores a config/history in the user's home, and recommends cron for scheduling. It references 'send alerts' but does not implement or describe external alert endpoints or notification mechanisms (no webhook/email provider configured), so alert delivery is undefined. The instructions do not ask for unrelated files, secrets, or other system credentials.
Install Mechanism
There is no install spec (instruction-only) and the scripts are included in the package; nothing is downloaded at install time. This minimizes install-time risk.
Credentials
The skill requests no environment variables or credentials and the scripts do not attempt to read secrets. They only perform network connections to the target sites and write config/history under the user's home directory.
Persistence & Privilege
always:false and no cross-skill/system-wide modifications. The skill stores config/history in ~/.openclaw/workspace by default — normal for a monitoring tool and not an elevated privilege.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install site-health-monitor
  3. After installation, invoke the skill by name or use /site-health-monitor
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Slug site-health-monitor
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Site Health Monitor?

Monitor websites for uptime, SSL certificate expiry, response time, HTTP errors, and content changes. Generate health reports and send alerts when issues are... It is an AI Agent Skill for Claude Code / OpenClaw, with 122 downloads so far.

How do I install Site Health Monitor?

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

Is Site Health Monitor free?

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

Which platforms does Site Health Monitor support?

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

Who created Site Health Monitor?

It is built and maintained by charlie-morrison (@charlie-morrison); the current version is v1.0.0.

💬 Comments