unified-notifications-ops
by affaan-munified-notifications-ops is an ECC-native skill for unifying GitHub, Linear, desktop, hook, chat, and email alerts into one operator lane. Use it to define routing, severity, ownership, deduplication, escalation, and follow-up action instead of scattered pings.
This skill scores 78/100, which means it is a solid listing candidate with enough real workflow value for directory users to consider installing. It is clearly aimed at a specific operational problem—unifying fragmented notifications across GitHub, Linear, hooks, desktop alerts, chat, and email—and the SKILL.md provides enough structure to reduce guesswork for an agent. The main caveat is that it is policy-heavy rather than execution-heavy, so users should expect guidance on notification orchestration more than a fully prescriptive implementation playbook.
- Clear triggerability: it explicitly says when to use it for alert routing, deduplication, escalation, and inbox collapse across known surfaces.
- Operationally scoped: the document describes a coherent ECC-native notification workflow with severity, ownership, routing, and follow-up action.
- Good install decision value: substantial body length with multiple headings and non-placeholder content signals a real skill rather than a stub.
- No scripts, references, or support files were provided, so agents must rely mainly on the SKILL.md policy text.
- The excerpt suggests broad orchestration guidance, but not a concrete step-by-step implementation workflow or examples for every connected tool.
Overview of unified-notifications-ops skill
unified-notifications-ops is a workflow skill for turning scattered alerts into one coherent operator lane. The unified-notifications-ops skill is best for people managing GitHub, Linear, desktop alerts, hooks, or chat/email notifications who need routing, deduplication, escalation, and follow-up action—not another generic “send a ping” prompt.
What unified-notifications-ops is for
Use unified-notifications-ops when the issue is notification sprawl: CI failures in one place, review requests in another, session events elsewhere, and no single policy for what deserves attention. The skill helps you define one ECC-native workflow that maps events to severity, ownership, and destination.
Who should install it
Install unified-notifications-ops if you already have signals coming from GitHub or connected tools and you want a clearer operational path. It is a strong fit for workflow automation setups where alert quality matters more than raw alert volume.
What makes it different
This skill emphasizes notification governance: source, severity, routing channel, and required follow-up. That makes unified-notifications-ops more useful than a prompt that only drafts a message, because it pushes you to decide how alerts should behave in practice.
How to Use unified-notifications-ops skill
Install unified-notifications-ops
Use the directory install flow shown in the repo, for example: npx skills add affaan-m/everything-claude-code --skill unified-notifications-ops. After install, confirm the skill is available in your agent environment before relying on it for workflow automation.
Read these files first
Start with skills/unified-notifications-ops/SKILL.md because it contains the operational rules and the intended event flow. Then inspect any linked repository context your environment provides, especially notes about routing, hooks, or tool boundaries. If your setup has no supporting files, treat SKILL.md as the source of truth.
Shape a better prompt
Good unified-notifications-ops usage starts with a concrete event picture. Include:
- the source system: GitHub, Linear, desktop, hook, email, or chat
- the event type: CI failure, PR review, issue update, escalation, or lifecycle event
- the desired severity and owner
- where the notification should land
- what should happen next
Example prompt shape: “Use unified-notifications-ops to define a GitHub and Linear alert path for failed CI on protected branches, suppress duplicates, and route urgent failures to desktop plus a follow-up issue.”
What to check before you ship
Look for hidden ambiguity in source mapping and escalation rules. The skill works best when you already know which events matter, which should be suppressed, and which require human follow-up. If those decisions are unclear, resolve them first or the workflow will stay noisy.
unified-notifications-ops skill FAQ
Is unified-notifications-ops only for GitHub?
No. GitHub is a common source, but unified-notifications-ops also fits Linear, desktop notifications, hooks, and connected communication surfaces. The point is to unify operational signals, not to lock you into one product.
When should I not use this skill?
Skip unified-notifications-ops if you only need a one-off message, a simple reminder, or a basic notification template. It is meant for workflow automation decisions where routing, deduplication, and escalation need to be designed.
Is this better than a normal prompt?
Usually yes when the problem is recurring. A normal prompt can draft text, but unified-notifications-ops helps you define the notification system itself: what triggers it, who sees it, and what action it should demand.
Is it beginner-friendly?
Yes, if you can describe a few real alerts you already receive. You do not need a full architecture diagram to start, but you do need enough context to distinguish signal from noise.
How to Improve unified-notifications-ops skill
Give it a real alert map
The strongest unified-notifications-ops input is a small inventory of current signals: source, urgency, and desired destination. “GitHub PR reviews should go to desktop, CI on main should page the owner, and low-priority issue chatter should stay muted” is much more actionable than “improve notifications.”
State the suppression rules
Users often care most about reducing noise. Say which events should be deduplicated, delayed, batched, or ignored. That lets unified-notifications-ops design a policy instead of just expanding the alert stream.
Specify the handoff
The most useful outputs usually include a clear next step: acknowledge, create a follow-up issue, escalate, or archive. If the workflow ends at “notify,” results will be weaker than if you define what happens after the notification.
Iterate with one branch at a time
If the first pass feels broad, refine by branch: CI, reviews, issue updates, session hooks, then chat/email surfaces. This is the fastest way to improve unified-notifications-ops for Workflow Automation without overcomplicating the initial install.