Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Continuous local security monitoring daemon for Linux and macOS. Detects brute-force attacks, malware, privilege escalation, suspicious processes, file tampe...
Continuous local security monitoring daemon for Linux and macOS. Detects brute-force attacks, malware, privilege escalation, suspicious processes, file tampe...
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. Then review README.md for any prerequisites, environment setup, or post-install checks. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
ReefWatch is a lightweight host-based intrusion detection system (HIDS) that runs as a background daemon on the same machine as OpenClaw. It continuously monitors the local system for security threats and alerts the user through OpenClaw's messaging channels ONLY when something suspicious is detected.
ReefWatch runs as an independent Python process (not consuming LLM tokens) and communicates with OpenClaw via the local webhook endpoint (/hooks/wake) to alert the user. [Collectors] โ [Detection Engines] โ [Alert Manager] โ [OpenClaw Webhook] โ [User]
YARA: File and process scanning for malware, webshells, miners, ransomware Sigma: Log-based detection for brute-force, privilege escalation, lateral movement Custom Rules: System-specific checks (file integrity, process anomalies, network connections)
When the user asks to start ReefWatch or enable security monitoring: Verify dependencies are installed: pip3 install -r ~/.openclaw/workspace/skills/reefwatch/requirements.txt --quiet Download initial rulesets (first time only): python3 ~/.openclaw/workspace/skills/reefwatch/setup_rules.py Start the daemon: nohup python3 ~/.openclaw/workspace/skills/reefwatch/reefwatch_daemon.py \ --webhook-url "http://127.0.0.1:18789/hooks/wake" \ --webhook-token "${OPENCLAW_HOOKS_TOKEN}" \ --config ~/.openclaw/workspace/skills/reefwatch/reefwatch_config.yaml \ > ~/.openclaw/logs/reefwatch.log 2>&1 & echo $! > /tmp/reefwatch.pid Confirm to the user: "๐ชธ ReefWatch is now active. I'll alert you if any threats are detected."
kill $(cat /tmp/reefwatch.pid 2>/dev/null) 2>/dev/null && rm -f /tmp/reefwatch.pid Confirm: "๐ชธ ReefWatch stopped."
if kill -0 $(cat /tmp/reefwatch.pid 2>/dev/null) 2>/dev/null; then echo "ReefWatch is running (PID: $(cat /tmp/reefwatch.pid))" tail -5 ~/.openclaw/logs/reefwatch.log else echo "ReefWatch is not running" fi
tail -20 ~/.openclaw/workspace/skills/reefwatch/alert_history.jsonl | python3 -c "import sys,json; [print(json.dumps(json.loads(l),indent=2)) for l in sys.stdin]"
python3 ~/.openclaw/workspace/skills/reefwatch/setup_rules.py --update
When the user asks to scan a specific file or directory: python3 ~/.openclaw/workspace/skills/reefwatch/manual_scan.py --target <path>
When ReefWatch detects a threat, it wakes OpenClaw with a message like: ๐ด REEFWATCH ALERT โโโโโโโโโโโโโโโโโโ Type: Brute-force SSH attempt Severity: HIGH Source: auth.log Detail: 47 failed login attempts from 192.168.1.105 in 2 minutes Rule: sigma/ssh_brute_force Time: 2026-02-22 15:43:21 โโโโโโโโโโโโโโโโโโ Forward this alert to the user immediately through their active messaging channel. If the user asks for more details, check the full log at ~/.openclaw/logs/reefwatch.log.
ReefWatch does NOT consume LLM tokens while monitoring. It only triggers OpenClaw when alerting. On macOS, some collectors require granting Full Disk Access or specific permissions. YARA scanning can be CPU-intensive; default config scans changed files only, not full disk. The daemon auto-recovers if a collector fails; it logs the error and continues with remaining collectors. All data stays local. ReefWatch never sends system data to external servers (only to OpenClaw's local webhook).
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.