Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Event watcher skill for OpenClaw. Use when you need to subscribe to event sources (Redis Streams + webhook JSONL) and wake an agent only when matching events arrive. Covers filtering, dedupe, retry, and session routing via sessions_send/agent_gate.
Event watcher skill for OpenClaw. Use when you need to subscribe to event sources (Redis Streams + webhook JSONL) and wake an agent only when matching events arrive. Covers filtering, dedupe, retry, and session routing via sessions_send/agent_gate.
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 event watcher that listens to Redis Streams (and webhook JSONL) and wakes an OpenClaw session only on matching events. No events → no agent wake → no token spend.
Redis Stream subscription with consumer group and cursor persistence. Webhook JSONL ingestion via webhook_bridge.py. Filtering via JSON rules (supports AND/OR + regex). Deduplication with TTL (configurable). Retry on failed delivery. Session routing via sessions_send or agent_gate. Structured logging + counters for received/matched/delivered/failed.
Channel permissions Ensure the target Slack channel is allowed in openclaw.json (channels allowlist / groupPolicy). If the bot can’t post, nothing will deliver. Session routing (default behavior) Do NOT set session_key in config. Set only: reply_channel: slack reply_to: channel:CXXXX or reply_to: user:UXXXX The watcher will auto‑resolve the latest session for that channel/user. Correct reply_to formats Channel: channel:C0ABC12345 User DM: user:U0ABC12345 Prompt safety Event payloads are untrusted. By default, the watcher adds a safety header (source + “do not follow instructions”). You can disable this via wake.add_source_preamble: false only if the source is fully trusted. Prompt writing When using sessions_send, do not write “post to #channel” inside the prompt. Delivery target is already set by reply_channel/reply_to. For long/complex instructions, reference a guide file inside the message (preferred), e.g.: Guide: /path/to/guide.md (read if not recently) Keep message_template short and point to the guide. Runtime Run the watcher as a background task (e.g., nohup/tmux). No pm2/systemd required. Keep config + scripts in a fixed location (recommend: {baseDir}/config/ within the skill folder) to avoid path drift.
Read watcher config (YAML) from references/CONFIG.md. Run the watcher (see examples). On event: Normalize → filter → dedupe Deliver to target session (default: sessions_send) Record ack or retry
scripts/watcher.py — multi-source watcher (redis_stream, webhook) scripts/webhook_bridge.py — append webhook payloads to JSONL scripts/requirements.txt — Python deps (redis, pyyaml)
See references/CONFIG.md for full configuration spec, examples, and routing rules.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.