Notification Filter — Telegram vs Silent Routing

What problem does it solve?

This Skill prevents notification spam by routing security-research pipeline events either to Telegram for high-value signals or to silent logging for low-value noise.

Core Features & Use Cases

• Deduplicated alerting: Suppresses repeated events of the same type and token within a configurable time window to reduce repetitive chatter.
• Rule-based Telegram vs silent decisions: Sends messages using prioritized SEND rules (based on event type, score ranges, pipeline transitions, outreach lifecycle, revenue/cost/cap thresholds, and reminders) while logging non-matching events as SILENT.
• Operational exceptions: Always sends prayer_reminder notifications and bypasses dedup to ensure critical reminders are never missed.
• JVR receipt compliance: Produces a consistent “notification” receipt indicating whether Telegram was sent or silent logging occurred, including the matched rule (S-XX or Q-XX).

Quick Start

Configure TELEGRAM_CHAT_ID and DEDUP_WINDOW_MINUTES, then route orchestrator post-action events through this skill so scoring and pipeline events trigger Telegram alerts while low-value events remain silently logged.