Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.
Unified Notifications Ops is an ECC-native operational skill designed to consolidate fragmented notification streams across development, project management, and communication tools into a single coherent workflow. It addresses the common problem where important signals are scattered across GitHub, Linear, local hooks, desktop alerts, chat, and email, leading to missed context, duplicated noise, and reduced operator clarity. Instead of treating notifications as isolated events, it reframes them as part of a structured routing and escalation system focused on actionable outcomes.
Core capabilities center around an event pipeline that captures incoming signals, classifies urgency and ownership, routes them to appropriate channels, collapses duplicates, and attaches a clear next action for operators. It emphasizes severity modeling with defined tiers (critical, high, medium, low) and enforces rules such as digest-first defaults, suppression of low-signal noise, and strict separation of event source, routing, severity, and action. The workflow also includes inventorying existing notification surfaces, identifying overlaps, and designing an ECC-native orchestration layer that prefers existing hooks and primitives over introducing external tooling. A key constraint is avoiding over-notification by preventing fan-out across multiple channels unless justified by severity and necessity.
This skill is primarily used in environments with CI/CD pipelines, collaborative code review systems, and issue-tracking workflows where notification overload is common. It is particularly valuable for software engineers, SREs, platform engineers, and product operations teams who need to reduce alert fatigue while maintaining awareness of critical system events such as failed deployments, security issues, or blocked releases. It is also useful when consolidating legacy notification systems into a unified operational policy or when designing new workflows that require clear ownership and escalation paths.
It treats all incoming events as part of a single pipeline where they are captured, classified, routed, deduplicated, and assigned an action. Instead of forwarding raw alerts from each tool independently, it consolidates them into a structured workflow that prioritizes clarity and reduces redundancy.
It is designed to operate on top of existing notification sources such as development, issue tracking, and hook-based systems. The emphasis is on using what already exists rather than requiring new external notification platforms.
No. It does not replace underlying systems but reorganizes and orchestrates their outputs into a more coherent and actionable structure.
Severity is modeled into tiers such as critical, high, medium, and low. Each incoming event is classified based on urgency and operational impact, which then determines whether it triggers an interruption, a same-day alert, a digest, or suppression.
Quick Setup:
.claude/skills/Repository
affaan-m/everything-claude-code