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
Preferred Surface
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.
Non-Negotiable Rules
- never expose tokens, secrets, webhook secrets, or internal identifiers
- separate:
- event source
- severity
- routing channel
- operator action
- default to digest-first when interruption cost is unclear
- do not fan out every event to every channel
- if the real fix is better issue triage, hook policy, or project flow, say so explicitly
Event Pipeline
Treat the lane as:
- Capture the event
- Classify urgency and owner
- Route to the correct channel
- Collapse duplicates and low-signal churn
- Attach the next operator action
The goal is fewer, better notifications.
Default Severity Model
| Class |
Examples |
Default handling |
| Critical |
broken default-branch CI, security issue, blocked release, failed deploy |
interrupt now |
| High |
review requested, failing PR, owner-blocking handoff |
same-day alert |
| Medium |
issue state changes, notable comments, backlog movement |
digest or queue |
| Low |
repeat successes, routine churn, redundant lifecycle markers |
suppress or fold |
If the workspace has no severity model, build one before proposing automation.
Workflow
1. Inventory the current surface
List:
- event sources
- current channels
- existing hooks/scripts that emit alerts
- duplicate paths for the same event
- silent failure cases where important things are not being surfaced
Call out what ECC already owns.
2. Decide what deserves interruption
For each event family, answer:
- who needs to know?
- how fast do they need to know?
- should this interrupt, batch, or just log?
Use these defaults:
- interrupt for release, CI, security, and owner-blocking events
- digest for medium-signal updates
- log-only for telemetry and low-signal lifecycle markers
3. Collapse duplicates before adding channels
Look for:
- the same PR event appearing in GitHub, Linear, and local logs
- repeated hook notifications for the same failure
- comments or status churn that should be summarized instead of forwarded raw
- channels that duplicate each other without adding a better action path
Prefer:
- one canonical summary
- one owner
- one primary channel
- one fallback path
4. Design the ECC-native workflow
For each real notification need, define:
- source
- gate
- shape: immediate alert, digest, queue, or dashboard-only
- channel
- action
If ECC already has the primitive, prefer:
- a skill for operator triage
- a hook for automatic emission/enforcement
- an agent for delegated classification
- an MCP/connector only when a real bridge is missing
5. Return an action-biased design
End with:
- what to keep
- what to suppress
- what to merge
- what ECC should wrap next
Output Format
CURRENT SURFACE
- sources
- channels
- duplicates
- gaps
EVENT MODEL
- critical
- high
- medium
- low
ROUTING PLAN
- source -> channel
- why
- operator owner
CONSOLIDATION
- suppress
- merge
- canonical summaries
NEXT ECC MOVE
- skill / hook / agent / MCP
- exact workflow to build next
Recommendation Rules
- prefer one strong lane over many weak ones
- prefer digests for medium and low-signal updates
- prefer hooks when the signal should emit automatically
- prefer operator skills when the work is triage, routing, and review-first decision-making
- prefer
project-flow-ops when the root cause is backlog / PR coordination rather than alerts
- prefer
workspace-surface-audit when the user first needs a source inventory
- if desktop notifications are enough, do not invent an unnecessary external bridge
Good Use Cases
- "We have GitHub, Linear, and local hook alerts, but no single operator flow"
- "Our CI failures are noisy and people ignore them"
- "I want one notification policy across Claude, OpenCode, and Codex surfaces"
- "Figure out what should interrupt versus land in a digest"
- "Collapse overlapping notification PR ideas into one canonical ECC lane"
Related Skills
workspace-surface-audit
project-flow-ops
github-ops
knowledge-ops
customer-billing-ops when the notification pain is billing/customer operations rather than engineering
1---2name: unified-notifications-ops3description: 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.4metadata:5 source: https://skillmd.com/skills/mhassan0000/unified-notifications-ops6 origin: ECC7---89# Unified Notifications Ops1011Use this skill when the real problem is not a missing ping. The real problem is a fragmented notification system.1213The job is to turn scattered events into one operator surface with:14- clear severity15- clear ownership16- clear routing17- clear follow-up action1819## When to Use2021- the user wants a unified notification lane across GitHub, Linear, local hooks, desktop alerts, chat, or email22- CI failures, review requests, issue updates, and operator events are arriving in disconnected places23- the current setup creates noise instead of action24- the user wants to consolidate overlapping notification branches or backlog proposals into one ECC-native lane25- the workspace already has hooks, MCPs, or connected tools, but no coherent notification policy2627## Preferred Surface2829Start from what already exists:30- GitHub issues, PRs, reviews, comments, and CI31- Linear issue/project movement32- local hook events and session lifecycle signals33- desktop notification primitives34- connected email/chat surfaces when they actually exist3536Prefer ECC-native orchestration over telling the user to adopt a separate notification product.3738## Non-Negotiable Rules3940- never expose tokens, secrets, webhook secrets, or internal identifiers41- separate:42 - event source43 - severity44 - routing channel45 - operator action46- default to digest-first when interruption cost is unclear47- do not fan out every event to every channel48- if the real fix is better issue triage, hook policy, or project flow, say so explicitly4950## Event Pipeline5152Treat the lane as:53541. **Capture** the event552. **Classify** urgency and owner563. **Route** to the correct channel574. **Collapse** duplicates and low-signal churn585. **Attach** the next operator action5960The goal is fewer, better notifications.6162## Default Severity Model6364| Class | Examples | Default handling |65| --- | --- | --- |66| Critical | broken default-branch CI, security issue, blocked release, failed deploy | interrupt now |67| High | review requested, failing PR, owner-blocking handoff | same-day alert |68| Medium | issue state changes, notable comments, backlog movement | digest or queue |69| Low | repeat successes, routine churn, redundant lifecycle markers | suppress or fold |7071If the workspace has no severity model, build one before proposing automation.7273## Workflow7475### 1. Inventory the current surface7677List:78- event sources79- current channels80- existing hooks/scripts that emit alerts81- duplicate paths for the same event82- silent failure cases where important things are not being surfaced8384Call out what ECC already owns.8586### 2. Decide what deserves interruption8788For each event family, answer:89- who needs to know?90- how fast do they need to know?91- should this interrupt, batch, or just log?9293Use these defaults:94- interrupt for release, CI, security, and owner-blocking events95- digest for medium-signal updates96- log-only for telemetry and low-signal lifecycle markers9798### 3. Collapse duplicates before adding channels99100Look for:101- the same PR event appearing in GitHub, Linear, and local logs102- repeated hook notifications for the same failure103- comments or status churn that should be summarized instead of forwarded raw104- channels that duplicate each other without adding a better action path105106Prefer:107- one canonical summary108- one owner109- one primary channel110- one fallback path111112### 4. Design the ECC-native workflow113114For each real notification need, define:115- **source**116- **gate**117- **shape**: immediate alert, digest, queue, or dashboard-only118- **channel**119- **action**120121If ECC already has the primitive, prefer:122- a skill for operator triage123- a hook for automatic emission/enforcement124- an agent for delegated classification125- an MCP/connector only when a real bridge is missing126127### 5. Return an action-biased design128129End with:130- what to keep131- what to suppress132- what to merge133- what ECC should wrap next134135## Output Format136137```text138CURRENT SURFACE139- sources140- channels141- duplicates142- gaps143144EVENT MODEL145- critical146- high147- medium148- low149150ROUTING PLAN151- source -> channel152- why153- operator owner154155CONSOLIDATION156- suppress157- merge158- canonical summaries159160NEXT ECC MOVE161- skill / hook / agent / MCP162- exact workflow to build next163```164165## Recommendation Rules166167- prefer one strong lane over many weak ones168- prefer digests for medium and low-signal updates169- prefer hooks when the signal should emit automatically170- prefer operator skills when the work is triage, routing, and review-first decision-making171- prefer `project-flow-ops` when the root cause is backlog / PR coordination rather than alerts172- prefer `workspace-surface-audit` when the user first needs a source inventory173- if desktop notifications are enough, do not invent an unnecessary external bridge174175## Good Use Cases176177- "We have GitHub, Linear, and local hook alerts, but no single operator flow"178- "Our CI failures are noisy and people ignore them"179- "I want one notification policy across Claude, OpenCode, and Codex surfaces"180- "Figure out what should interrupt versus land in a digest"181- "Collapse overlapping notification PR ideas into one canonical ECC lane"182183## Related Skills184185- `workspace-surface-audit`186- `project-flow-ops`187- `github-ops`188- `knowledge-ops`189- `customer-billing-ops` when the notification pain is billing/customer operations rather than engineering