Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Create monitors for anything. User defines what to check, skill handles scheduling and alerts.
Create monitors for anything. User defines what to check, skill handles scheduling and alerts.
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.
~/monitor/ โโโ monitors.json # Monitor definitions โโโ config.json # Alert preferences โโโ logs/ # Check results โโโ {name}/YYYY-MM.jsonl Create on first use: mkdir -p ~/monitor/logs
This skill: โ Stores monitor definitions in ~/monitor/ โ Runs checks at specified intervals โ Alerts user on status changes Execution model: User explicitly defines WHAT to monitor User grants any permissions/tools needed Skill only handles WHEN and ALERTING This skill does NOT: โ Assume access to any service or endpoint โ Run checks without user-defined instructions โ Store credentials (user provides via environment or other skills)
Required: curl โ for HTTP checks Optional (for alerts): PUSHOVER_TOKEN / PUSHOVER_USER โ for push notifications Webhook URL โ user provides their own endpoint Used if available: openssl โ for SSL certificate checks pgrep โ for process checks df โ for disk space checks nc โ for port checks
TopicFileMonitor type examplestemplates.mdAlert configurationalerts.mdAnalysis patternsinsights.md
When user requests a monitor: WHAT: User specifies what to check HOW: User provides method or grants tool access WHEN: This skill handles interval ALERT: This skill handles notifications Example flow: User: "Monitor my API at api.example.com every 5 minutes" Agent: "I'll check HTTP status. Alert you on failures?" User: "Yes, and check SSL cert too" โ Monitor stored with user-defined checks
In ~/monitor/monitors.json: { "api_prod": { "description": "User's API health", "checks": [ {"type": "http", "target": "https://api.example.com/health"}, {"type": "ssl", "target": "api.example.com"} ], "interval": "5m", "alert_on": "change", "requires": [], "created": "2024-03-15" } }
User can request any of these (or others): TypeWhat it checksTool usedhttpURL status + latencycurlsslCertificate expiryopensslprocessProcess runningpgrepdiskFree spacedfportPort opennccustomUser-defined commanduser specifies
โ Monitor: [description] ๐ Checks: [what will be checked] โฑ๏ธ Interval: [how often] ๐ Alert: [when to notify] ๐ง Requires: [tools/access needed]
Alert when status changes (okโfail, failโok) Include failure count Recovery message when back to OK Never spam repeated same-status
The requires field lists what user granted: Empty = basic checks only (curl, df, pgrep) ["ssh:server1"] = user granted SSH access ["docker"] = user granted Docker access Agent asks before assuming any access.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.