New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Notification Routing

by bradygaster in bradygaster/squad

Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding

MITAuto-check passedBackend & APIs

Install Notification Routing

skills CLI
$ npx skills add bradygaster/squad --skill notification-routing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bradygaster/squad notification-routing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bradygaster/squad.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.squad-templates/skills/notification-routing .claude/skills/notification-routing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
notification-routing
GitHub stars
3.3k
Token cost
~770 tokens
SKILL.md length
250 words
Files
1
Skills in repo
31
Repo updated
First seen
Licence
MIT

At a glance

Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding

  • Tasks that involve Event-driven systems
  • SKILL.md covers Context, Patterns, Anti-Patterns and Distributed Systems Pattern
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Notification Routing is an agent skill from bradygaster/squad. Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding

Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Event-driven systems. The repository describes itself as: Squad: AI agent teams for any project. The licence is MIT.

When your agent uses it

  • Tasks that involve Event-driven systems

Example prompts

  • “/notification-routing”

What it can do on your machine

Read from SKILL.md and the folder at commit 1fd7e03. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json and bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Notification Routing loads about 770 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 250 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~770

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bradygaster/squad at commit 1fd7e03, republished under its MIT licence (© bradygaster). 250 words, ~770 tokens.

Download SKILL.mdSave it as .claude/skills/notification-routing/SKILL.md (or your agent's skills folder).
name
notification-routing
description
Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding
domain
communication
confidence
high
source
earned

Context

When a Squad grows beyond a few agents, notifications flood a single channel — failure alerts drown in daily briefings, tech news buries security findings, and everything gets ignored. This is the pub-sub problem: a single message queue for everything is a recipe for missed alerts.

The fix is topic-based routing: agents tag notifications with a channel type, and a routing function sends them to the appropriate destination.

Trigger symptoms:

  • Important alerts missed because they're buried in routine notifications
  • Team members turning off notifications entirely (signal overwhelm)
  • Onboarding friction: "where do I look for X?"

Patterns

Channel Config Schema

Define a .squad/teams-channels.json (or equivalent) mapping notification types to channel identifiers:

json
{
  "teamId": "your-team-id",
  "channels": {
    "notifications": "squad-alerts",
    "tech-news":     "tech-news",
    "security":      "security-findings",
    "releases":      "release-announcements",
    "daily-digest":  "daily-digest"
  }
}

Place this in .squad/ (git-tracked, shared across the team). For platforms that use channel IDs instead of names (Teams, Slack), store the resolved ID alongside the name to avoid name-collision bugs:

json
{
  "channels": {
    "notifications": { "name": "squad-alerts", "id": "channel-id-opaque-string" }
  }
}
CHANNEL: Tag Convention

Agents prefix their output with CHANNEL:<type> to signal where the notification should go:

CHANNEL:security
Security Reviewer found 3 new CVEs in dependency scan: lodash@4.17.15, minimist@1.2.5
Routing Dispatcher (shell pseudocode)
bash
dispatch_notification() {
  local raw_output="$1"
  local channel="notifications"  # default

  if echo "$raw_output" | grep -qE '^CHANNEL:[a-z][a-z0-9-]*'; then
    channel=$(echo "$raw_output" | head -1 | cut -d: -f2)
    raw_output=$(echo "$raw_output" | tail -n +2)
  fi

  send_notification --channel "$channel" --message "$raw_output"
}
Provider-Agnostic Adapter

The routing layer is provider-agnostic. Plug in your platform adapter:

.squad/notify-adapter.sh   # Teams / Slack / Discord / webhook -- swappable

The routing config and CHANNEL: tags never change. Only the adapter changes per deployment.

Anti-Patterns

Never send all notification types to one channel:

send_notification --channel "general" --message "$anything"

Never use display names as identifiers (name collision risk):

send_to_team --name "Squad" --channel "notifications"

Resolve channel IDs once at setup. Use IDs at runtime.

Distributed Systems Pattern

This is pub-sub with topic routing -- the same principle as Kafka topics, RabbitMQ routing keys, and AWS SNS topic filtering. Route by type. Each consumer subscribes to the topics it cares about.

© bradygaster, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .squad-templates/skills/notification-routing of bradygaster/squad.

Open the folder on GitHubat commit 1fd7e03

Compare with similar skills

Notification Routing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Notification Routing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Notification Routing this skillbradygaster/squad3.3k—~770Automated safety check: PassMIT
Stripe Projectsfossasia/eventyay1.7k5 repos~2kAutomated safety check: NotesApache-2.0
MQTTX CLIemqx/MQTTX5.1k—~1.9kAutomated safety check: PassApache-2.0
AWS Serverless Edazxkane/aws-skills3674 repos~3.2kAutomated safety check: PassMIT
Windmill Trigger Type Checklistwindmill-labs/windmill18k—~4.7kAutomated safety check: PassCustom licence
FoundatioFoundatioFx/Foundatio2.1k—~3.9kAutomated safety check: PassApache-2.0

Similar skills

  • Stripe Projects

    fossasia/eventyay

    A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.

    1.7k GitHub starsUsed in 5 repos~2k tokens
    Backend & APIsAuto-check: notes

  • MQTTX CLI

    emqx/MQTTX

    Operates the `mqttx` command line client to connect, publish, subscribe, benchmark and simulate data against an MQTT broker, with TLS and MQTT 5 support.

    5.1k GitHub stars~1.9k tokensUpdated 7 days ago
    Backend & APIsAuto-check passed

  • AWS Serverless Eda

    zxkane/aws-skills

    AWS serverless and event-driven architecture expert based on Well-Architected Framework.

    367 GitHub starsUsed in 4 repos~3.2k tokens
    Backend & APIsAuto-check passed

  • Windmill Trigger Type Checklist

    windmill-labs/windmill

    Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.

    18k GitHub stars~4.7k tokensUpdated today
    Backend & APIsAuto-check passed

  • Foundatio

    FoundatioFx/Foundatio

    A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.

    2.1k GitHub stars~3.9k tokensUpdated today
    Backend & APIsAuto-check passed

  • Homerail Dag Ops

    xiaotianfotos/homerail

    Design, start, supervise, inspect, and continue HomeRail DAG workflows from any agent with CLI or HTTP access.

    992 GitHub stars~1.5k tokensUpdated 13 days ago
    Backend & APIsAuto-check passed

More from bradygaster/squad

All 31 skills in this repo

  • Fact Checking

    bradygaster/squad

    Review and validate claims using counter-hypothesis testing.

    3.3k GitHub stars~503 tokensUpdated today
    Auto-check passed

  • Architectural Review

    bradygaster/squad

    How to review PRs for architectural quality — module boundaries, dependency direction, export surface, pattern consistency

    3.3k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Archival Integrity

    bradygaster/squad

    Preserve content when moving entries between tracked Squad state files

    3.3k GitHub stars~735 tokensUpdated today
    Auto-check passed

  • CI Validation Gates

    bradygaster/squad

    Defensive CI/CD patterns: semver validation, token checks, retry logic, and draft detection

    3.3k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • CLI Wiring

    bradygaster/squad

    Checklist and patterns for wiring new CLI commands into cli-entry.ts

    3.3k GitHub stars~501 tokensUpdated today
    Auto-check passed

  • Cross Machine Coordination

    bradygaster/squad

    Enables squad agents on different machines to share work via git-based task queuing

    3.3k GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Notification Routing

What does Notification Routing do?

Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding. Notification Routing is an agent skill from bradygaster/squad.

When should I use Notification Routing?

Notification Routing fits situations like: tasks that involve Event-driven systems.

How do I install Notification Routing in Claude Code?

Run `npx skills add bradygaster/squad --skill notification-routing -a claude-code`. Or copy the skill folder (.squad-templates/skills/notification-routing in bradygaster/squad) into .claude/skills/notification-routing in your project. Claude Code loads it when a task matches its description.

How do I install Notification Routing in Codex?

Run `npx skills add bradygaster/squad --skill notification-routing -a codex`. Or copy the skill folder (.squad-templates/skills/notification-routing in bradygaster/squad) into .agents/skills/notification-routing in your project. Codex loads it when a task matches its description.

Can I use Notification Routing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bradygaster/squad --skill notification-routing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/notification-routing, .gemini/skills/notification-routing, .github/skills/notification-routing and .opencode/skills/notification-routing in your project.

What does Notification Routing need to run?

SKILL.md names no scripts, command-line tools or credentials: Notification Routing is instructions for the agent only.

Does Notification Routing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Notification Routing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Notification Routing use?

Notification Routing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Notification Routing use?

About 770 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Notification Routing?

Skills that share tags, products or a category with Notification Routing: Stripe Projects (fossasia/eventyay, 1.7k stars), MQTTX CLI (emqx/MQTTX, 5.1k stars), AWS Serverless Eda (zxkane/aws-skills, 367 stars) and Windmill Trigger Type Checklist (windmill-labs/windmill, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Notification Routing?

bradygaster (a GitHub user) maintains it in bradygaster/squad, which has 3,257 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 8, 2026.

Source: bradygaster/squad on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.