skills.rest
seiggy
seiggyCOMMUNITY
Explore all skills by this author →
GitHub

notification-routing

Route agent notifications to topic-based channels using CHANNEL tags and a provider-agnostic dispatcher.

1|Updated Jul 7, 2026
Search Tags:#multi-agent#slack#teams#pub-sub#alert fatigue#topic routing#notification routing
One-click install
npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill notification-routing-seiggy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: notification-routing
Source: https://github.com/seiggy/maf-copilot-studio-demo/tree/main/.squad/templates/skills/notification-routing
Command: npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill notification-routing-seiggy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a multi-agent squad sends every alert to one channel, critical notifications get buried under routine messages, 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, tech-news, releases, daily-digest) to channel names and resolved IDs. - CHANNEL Tag Convention: Agents prefix output with CHANNEL:<type> so a dispatcher can strip the tag and route the message to the right destination. - Provider-Agnostic Adapter: Swap Teams, Slack, Discord, or webhook adapters without changing routing config or tags. - Use Case: A security agent finds new CVEs and emits CHANNEL:security; the dispatcher sends the finding to the security-findings channel instead of flooding the general alerts channel. ## Quick Start Set up topic-based notification routing for my agent squad so security alerts, tech news, and daily digests each go to their own channel.

Frequently Asked Questions about notification-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route agent notifications to different channels?▼

Tag each notification with a CHANNEL:<type> prefix and run it through a dispatcher function that reads the tag, looks up the channel in a JSON config, and sends the message to that destination. Untagged messages fall back to a default notifications channel.

How do I prevent alert fatigue in multi-agent systems?▼

Use topic-based routing so each notification type goes to its own channel instead of one shared feed. Team members subscribe only to the topics they care about, similar to Kafka topics or SNS topic filtering.

Can I use notification routing with Slack or Microsoft Teams?▼

Yes, the routing layer is provider-agnostic. Write a platform adapter script for Teams, Slack, Discord, or a generic webhook, and keep the channel config and CHANNEL tags unchanged when switching platforms.

Why should I use channel IDs instead of channel names?▼

Display names can collide across teams, causing messages to land in the wrong channel. Resolve channel IDs once at setup, store them alongside names in the config, and use the opaque IDs at runtime.

What happens when a notification has no channel tag?▼

The dispatcher assigns a default channel, typically the general notifications channel. This ensures untagged agent output is still delivered rather than dropped.

Related Skills

Explore More Software Engineering Skills→
RADHA0-maxRADHA0-max
2

init-first-agent

Creates the first NanoClaw agent for a DM channel and verifies welcome message delivery.

Community
Advanced
yashpanchalhqyashpanchalhq

alert-manager

Automate SEO monitoring and threshold-based alerts for rankings, traffic, and site health.

Community
Advanced
allthingslinuxallthingslinux
1

alert-management

Route alerts and coordinate incidents across PagerDuty, Alertmanager, and Slack.

Official
Advanced
ankraioankraio
26

ankra-alerts-webhooks

Route cluster alerts to external systems via webhooks with AI incident context.

Official
Intermediate