notification-routing Skill
Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding Published by microsoft in frontier-agentic-devops-rvas.
What is notification-routing Skill?
Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding Published by microsoft in frontier-agentic-devops-rvas. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Security review use cases
Technical details
- Install or run with Copy skill directory
When to use notification-routing Skill
- Use it for security review.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/frontier-agentic-devops-rvas
- Skill file: .squad/templates/skills/notification-routing/SKILL.md
What it does
Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding
Skill instructions
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
Explore related resources
Frequently asked questions
What is notification-routing?
notification-routing is a open-source AI agent skill with Copy skill directory. Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding
Who is notification-routing best for?
notification-routing is best for reusing agent instructions, scripts, and references, security review workflows.
How do I install notification-routing?
Install or run notification-routing using Copy skill directory. Check notification-routing for the latest setup command.
Is notification-routing actively maintained?
notification-routing may need a closer maintenance check before production use.
Auto-fetched from GitHub.
