notification-routing

What problem does it solve?

Agents and automation pipelines often send all notifications to a single channel where important alerts are drowned by routine messages, causing missed incidents and notification fatigue. This Skill prescribes topic-based routing so each notification type reaches the right audience and stays visible.

Core Features & Use Cases

• Channel mapping: Define a persistent mapping of logical notification types to channel names or resolved channel IDs in a team configuration file.
• Message tagging convention: Use a simple CHANNEL:<type> prefix to let agents declare the intended audience for each message.
• Provider-agnostic adapters: Swap platform-specific adapters (Teams, Slack, Discord, webhooks) without changing routing logic.
• Use Case: Separate security findings from daily digests so engineers only receive high-priority security alerts in the security channel while routine reports go to a digest channel.

Quick Start

Send a notification prefixed with CHANNEL:security and ensure your .squad/teams-channels.json maps "security" to the target channel ID.