Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Monitors self-hosted services by checking HTTP endpoints, TCP ports, SSL expiry, and DNS resolution, then reports status and alerts in concise, chat-friendly...
Monitors self-hosted services by checking HTTP endpoints, TCP ports, SSL expiry, and DNS resolution, then reports status and alerts in concise, chat-friendly...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Lightweight service and endpoint monitoring for self-hosted infrastructure. Checks HTTP endpoints, TCP ports, SSL certificate expiry, and DNS resolution โ then reports status in a clean, chat-friendly format.
HTTP Health Checks โ GET/POST with expected status codes, response time tracking, content matching TCP Port Checks โ Verify services are listening (databases, mail servers, game servers, etc.) SSL Certificate Monitoring โ Days until expiry, issuer info, auto-warn thresholds DNS Resolution โ Verify domains resolve correctly, detect DNS hijacking Smart Summaries โ One-glance status for all your services, with trend data Alert Logic โ Configurable thresholds, cooldowns, and severity levels to prevent alert fatigue
Create watchdog.json in your workspace root: { "services": [ { "name": "Home Assistant", "type": "http", "url": "http://192.168.1.100:8123", "expect_status": 200, "timeout_ms": 5000 }, { "name": "Proxmox", "type": "https", "url": "https://proxmox.local:8006", "expect_status": 200, "ssl_warn_days": 14, "timeout_ms": 5000 }, { "name": "PostgreSQL", "type": "tcp", "host": "db.local", "port": 5432, "timeout_ms": 3000 }, { "name": "My Domain", "type": "dns", "domain": "example.com", "expect_ip": "93.184.216.34" } ], "defaults": { "timeout_ms": 5000, "ssl_warn_days": 14, "alert_cooldown_min": 30, "history_retention_days": 30 } }
bash skills/service-watchdog/watchdog.sh Output example: ๐ข Home Assistant โ 200 OK (142ms) ๐ข Proxmox โ 200 OK (89ms) | SSL: 47 days ๐ข PostgreSQL โ port 5432 open (12ms) ๐ข My Domain โ resolves to 93.184.216.34 โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ 4/4 healthy | avg response: 81ms | checked: 2026-02-24 16:30 UTC
bash skills/service-watchdog/watchdog.sh --report Shows trend data: uptime percentage, P95 response times, incident history.
bash skills/service-watchdog/watchdog.sh --json
bash skills/service-watchdog/watchdog.sh --ssl-only
bash skills/service-watchdog/watchdog.sh --alerts-only Only outputs services that need attention (down, slow, SSL expiring).
Add to your OpenClaw cron for continuous monitoring: Every 5 minutes (lightweight check): Run `bash skills/service-watchdog/watchdog.sh --json` and report only if any service is unhealthy. Daily SSL report: Run `bash skills/service-watchdog/watchdog.sh --ssl-only` and report expiring certificates.
TypeRequired FieldsOptional Fieldshttp / httpsurlexpect_status, expect_body, method, headers, timeout_ms, ssl_warn_daystcphost, porttimeout_msdnsdomainexpect_ip, nameserver
FieldDefaultDescriptiontimeout_ms5000Request timeoutssl_warn_days14SSL expiry warning thresholdalert_cooldown_min30Min minutes between repeated alertshistory_retention_days30How long to keep check historyhistory_filewatchdog-history.csvPath for check history data
When the user asks about service status, infrastructure health, or "are my services up?": Run bash skills/service-watchdog/watchdog.sh for a quick overview Run with --report for detailed trends and history Run with --alerts-only for just the problems Run with --ssl-only to check certificate status Run with --json when you need structured data for further analysis For proactive monitoring, run checks in cron jobs and only alert the user when something is wrong.
curl (for HTTP/HTTPS checks) openssl (for SSL certificate checks) nc or ncat (for TCP port checks) โ falls back to bash /dev/tcp if unavailable dig or nslookup (for DNS checks) โ falls back to host command jq (for JSON config parsing) All standard on most Linux distributions. No external APIs or accounts needed.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.