unified-notifications-ops

What problem does it solve?

Fragmented notifications across GitHub, Linear, local hooks, desktop alerts, and connected communication surfaces create noise, duplicate signals, unclear ownership, and missed escalations. This Skill guides designing a single MCC-native operator surface that classifies severity, assigns ownership, collapses duplicates, and routes the right action to the right channel. The outcome is fewer, clearer notifications that drive operator action instead of inbox overload.

Core Features & Use Cases

• Inventory & Audit: list event sources, channels, duplicate paths, and silent failure cases to understand the current surface.
• Severity & Ownership Model: define critical/high/medium/low classifications and map owners for each event family.
• Routing & Deduplication: design rules that route interruptions, batch digests, and collapse duplicate signals into canonical summaries.
• MCC-native Execution: prefer skills, hooks, agents, or MCPs to implement automation while keeping tokens and secrets private.
• Use Case: reduce noisy CI and PR alerts by consolidating GitHub, Linear, and local hook events into a single digest-plus-interrupt workflow with clear owners and fallback channels.

Quick Start

Run a workspace inventory of GitHub, Linear, local hooks, and desktop notification sources and produce a routing plan that classifies events by severity and owner.