Agent skill · Workflow & Productivity

unified-notifications-ops

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.

mturacgithub.com/mturacGitHub ↗
codexcopilotcursorMIT
Install
npx skills add mturac/everything-openai-codex --skill unified-notifications-ops --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/unified-notifications-ops/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 84
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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, secret

What's inside
Steps it walks through
  1. When to Use
  2. Preferred Surface
  3. Non-Negotiable Rules
  4. Event Pipeline
  5. Default Severity Model
  6. Workflow
  7. 1. Inventory the current surface
  8. 2. Decide what deserves interruption
  9. 3. Collapse duplicates before adding channels
  10. 4. Design the ecc-native workflow
  11. 5. Return an action-biased design
  12. Output Format
  13. Recommendation Rules
  14. Good Use Cases
More from everything-openai-codex
All skills →
About this skill
What does the unified-notifications-ops skill do?

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.

How do I install it?

Run `npx skills add mturac/everything-openai-codex --skill unified-notifications-ops --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going