What problem does it solve? When a multi-agent team grows, all notifications flood a single channel — critical security alerts get buried under daily digests and tech news, causing missed alerts and notification fatigue. This Skill implements topic-based routing so each notification type reaches its own channel. ## Core Features & Use Cases - Channel Config Schema: Define a .squad/teams-channels.json mapping notification types (security, releases, daily-digest) to channel names or opaque IDs, avoiding name-collision bugs. - CHANNEL: Tag Convention: Agents prefix output with CHANNEL:<type> so a dispatcher can parse the tag and route the message to the correct destination. - Provider-Agnostic Adapter: A swappable adapter script (Teams, Slack, Discord, webhook) keeps routing config stable while the delivery platform changes. - Use Case: A security agent finds new CVEs in a dependency scan; it tags output CHANNEL:security, and the dispatcher sends the finding only to the security-findings channel instead of the general feed. ## Quick Start Set up topic-based notification routing for my agent team by creating a channels config and tagging agent output with CHANNEL prefixes.
