unified-notifications-ops

Consolidates notifications from GitHub, Linear, desktop alerts and messaging into one ECC-native workflow with routing, deduplication, escalation, inbox collapse, and secure handling of secrets.

86|21|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill unified-notifications-ops-jamkris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unified-notifications-ops
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/unified-notifications-ops
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill unified-notifications-ops-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fragmented notifications across multiple tools (GitHub, Linear, desktop alerts, and hooks) create noise and slow responses. This skill unifies them into one ECC-native workflow, enabling clear ownership, routing, and follow-up actions.

Core Features & Use Cases

  • ECC-native orchestration of cross-tool notifications
  • Clear routing, deduplication, escalation, and inbox-collapse strategies
  • Seamless integration with existing hooks, MCPs, and connected surfaces to enforce a coherent notification policy

Quick Start

Enable the unified notifications lane and point your sources to the ECC-native workflow.

Frequently Asked Questions about unified-notifications-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate scattered notifications from GitHub and Linear into a single workflow?▼

You can consolidate scattered notifications by pointing sources like GitHub and Linear into an ECC-native workflow, enforcing a structured pipeline with source, severity, routing, and action to unify alert management.

What is the best way to deduplicate and escalate alerts across multiple messaging surfaces?▼

The best way to deduplicate and escalate alerts is to apply a structured notification policy that collapses inboxes and enforces routing rules across multiple messaging surfaces within a unified workflow.

Does this notification routing approach work with existing hooks and connected surfaces?▼

Yes, this notification routing approach seamlessly integrates with existing hooks, MCPs, and connected surfaces to enforce a coherent notification policy across your current tools.

How do I collapse noisy alert inboxes without exposing tokens or secrets?▼

You collapse noisy alert inboxes by routing alerts through a structured pipeline that enforces source, severity, and action metadata while ensuring tokens and secrets are never exposed.

Can I apply custom routing and severity rules to desktop alerts and messaging notifications?▼

Yes, you can apply custom routing and severity rules to desktop alerts and messaging notifications by orchestrating them through the ECC-native workflow with structured pipeline enforcement.