skills.rest
DeDuva
DeDuvaCOMMUNITY
Explore all skills by this author →
GitHub

notification-routing

Route notifications by type to dedicated channels via a dispatcher and adapter.

1|Updated Apr 18, 2026
Search Tags:#routing#channels#notifications#adapter#pubsub#team-communication
One-click install
npx skills add https://github.com/DeDuva/squad --skill notification-routing-deduva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: notification-routing
Source: https://github.com/DeDuva/squad/tree/main/packages/squad-cli/templates/skills/notification-routing
Command: npx skills add https://github.com/DeDuva/squad --skill notification-routing-deduva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams rely on a single alert channel, important messages get buried and fatigue grows. This skill routes agent notifications to distinct channels based on type to keep critical alerts visible and organized.

Core Features & Use Cases

  • Channel Config Schema: define a centralized .squad/teams-channels.json mapping notification types to channel identifiers.
  • CHANNEL: Tag Convention: agents prepend CHANNEL:<type> to route messages to the correct destination.
  • Routing Dispatcher: a dispatcher that reads the type tag and forwards the notification to the chosen channel.
  • Provider-agnostic Adapter: swap in your platform's adapter (Teams/Slack/Discord/webhook) without changing routing logic.

Quick Start

Configure channel mappings and deploy the routing adapter to start directing notifications by type.

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 to reduce alert fatigue?▼

You can route agent notifications to dedicated channels by type using a centralized mapping schema and a routing dispatcher, keeping critical alerts visible and organized to directly reduce alert fatigue.

Can I send specific notification types like security findings to a dedicated Slack or Discord channel?▼

Yes, specific notification types like security findings can be routed to dedicated Slack or Discord channels using a provider-agnostic adapter, allowing platform swaps without altering the underlying routing logic.

How do agents tag messages so the dispatcher knows which channel to forward them to?▼

Agents prepend a CHANNEL type tag to messages, which the routing dispatcher reads to automatically forward the notification to the correct destination channel defined in your configuration.

What is the best way to organize multi-agent team communication across multiple channels?▼

Organizing multi-agent team communication is best handled by implementing a centralized channel configuration schema, mapping distinct alert types to separate channels to prevent important messages from getting buried.

Do I need to change my routing logic if I switch notification providers from Teams to webhooks?▼

No, you do not need to change routing logic when switching providers because the skill uses a provider-agnostic adapter, letting you swap platforms like Teams, Slack, Discord, or webhooks seamlessly.

When should I implement per-type routing for project alerts instead of using a single channel?▼

You should implement per-type routing for complex projects and multi-agent teams when a single alert channel becomes overwhelmed, causing message burial and growing alert fatigue among team members.

Related Skills

Explore More Content & Communication Skills→
Leep-GHLeep-GH

notification-routing

Route agent notifications to channels by type using CHANNEL tags.

Community
Intermediate
Hyeonjun0527Hyeonjun0527
1

configure-notifications

Configure Telegram, Discord, and Slack notification integrations with validation and test messaging.

Community
Advanced
AshleyHollisAshleyHollis

notification-routing

Route agent notifications to configured channels by type.

Community
Intermediate
pextacypextacy

configure-notifications

Configure OMX notifications for Discord, Telegram, Slack, and webhooks via YAML.

Community
Advanced