Unified Notifications Ops

This is the skill you reach for when you've got GitHub notifications, Linear updates, CI alerts, and desktop pings all screaming at you from different directions and you can't tell what actually needs your attention right now. It treats notifications as an ops problem: capture, classify by severity, route to the right channel, collapse duplicates, and attach the next action. The workflow is inventory your current mess, decide what deserves to interrupt versus digest versus suppress, then build one ECC-native lane instead of duct-taping together five separate tools. The honest take is that most notification problems are really triage and routing problems, and this skill makes you design a severity model before automating anything.

skills.sh installs: 3.5K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill unified-notifications-ops --agent claude-code

Installs into .claude/skills of the current project.

Files

Unified Notifications Ops

Use this skill when the real problem is not a missing ping. The real problem is a fragmented notification system.

The job is to turn scattered events into one operator surface with:

clear severity
clear ownership
clear routing
clear follow-up action

When to Use

the user wants a unified notification lane across GitHub, Linear, local hooks, desktop alerts, chat, or email
CI failures, review requests, issue updates, and operator events are arriving in disconnected places
the current setup creates noise instead of action
the user wants to consolidate overlapping notification branches or backlog proposals into one ECC-native lane
the workspace already has hooks, MCPs, or connected tools, but no coherent notification policy