notification-routing

Route agent notifications to channels by type using CHANNEL tags.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill notification-routing-leep-gh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notification-routing
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/packages/squad-cli/templates/skills/notification-routing
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill notification-routing-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Notifications across a growing Squad can flood a single channel, causing important alerts to be missed. Routing by type keeps alerts organized and actionable.

Core Features & Use Cases

  • Channel Config Schema: Define a .squad/teams-channels.json mapping notification types to channel identifiers and store it in version control for consistency.
  • CHANNEL: Tag Convention: Agents prefix their outputs with CHANNEL:<type> to signal destination.
  • Routing Dispatcher: A lightweight dispatcher reads the channel tag and forwards messages to the appropriate destination.
  • Provider-Agnostic Adapter: Use a plug-in adapter (.squad/notify-adapter.sh) to connect to Teams, Slack, Discord, or webhooks without changing the routing logic.

Quick Start

Tag a sample alert with CHANNEL:notifications and verify it reaches the correct 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 specific channels by type?

Route agent notifications by having agents prefix outputs with CHANNEL:<type> tags, which a dispatcher reads to forward messages to the correct channel. This prevents alert fatigue in squads with multiple notification types across platforms.

What is the best way to prevent alert fatigue in a squad with multiple notification types?

Preventing alert fatigue involves routing notifications by type to keep alerts organized and actionable. By mapping notification types to specific channel identifiers, important alerts are separated from daily digests and tech updates.

Does notification routing work with Slack, Discord, and Microsoft Teams?

Notification routing works with Teams, Slack, Discord, or webhooks through a provider-agnostic plug-in adapter. The adapter connects to your chosen platform without requiring changes to the underlying routing logic.

How do I configure channel mapping for squad notifications?

Configure channel mapping by defining a .squad/teams-channels.json file that maps notification types to channel identifiers. Store this file in version control to maintain consistency across your squad's notification routing.

Do I need a specific adapter script to dispatch notifications to different platforms?

You need a provider-agnostic adapter script located at .squad/notify-adapter.sh to dispatch notifications. This plug-in adapter connects the routing dispatcher to your target platforms without altering the core routing logic.

Why are my agent alerts being missed in a single crowded channel?

Agent alerts are missed because notifications across a growing squad flood a single channel. Routing by type separates alerts, tech updates, security findings, and daily digests into dedicated channels to keep them actionable.