unified-notifications-ops

Topics in the source

• Unified Notifications Ops
• When to Use
• Preferred Surface
• Non-Negotiable Rules
• Event Pipeline
• Default Severity Model
• Workflow
• 1. Inventory the current surface

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 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 Start from what already exists: GitHub issues, PRs, reviews, comments, and CI Linear issue/project movement local hook events and session lifecycle signals desktop notification primitives connected email/chat surfaces when they actually exist Prefer ECC-native orchestration over telling the user to adopt a separate notification product. never expose tokens, secrets, webhook secrets, or internal identifiers separate: event source severity routing channel operator action default to

This is an excerpt. Refer to the complete source and its current requirements.