tophant-clawvault-openclaw-alerts

To send high-risk security alerts to an OpenClaw agent, you can automate polling ClawVault dashboard endpoints, filter events by threat level, apply rate limiting, and deliver redacted messages to your configured agent session.

The best way to generate a daily security summary from ClawVault is by polling summary, budget, monitor, and scan history endpoints, then consolidating the data into a privacy-preserving daily report delivered to OpenClaw.

Yes, the OpenClaw alerts integration redacts sensitive content by default, ensuring that raw prompts, complete file paths, command text, and credential material are not sent unless explicitly enabled.

To prevent notification storms when monitoring ClawVault scan events, the system applies deduplication logic and rate limiting to ensure only eligible, high-risk events trigger operational messages.

Yes, you need a YAML skill configuration and state file under the ~/.ClawVault/openclaw-alerts/ directory to define polling behavior, delivery targets, and redaction rules for incident notifications.

Security events that trigger incident notifications in OpenClaw include prompt injection detection, secret or credential pattern matches, and high-risk block, ask_user, or sanitize actions recorded in scan history.