notification-hub

Aggregate and prioritize skill notifications into a low-noise delivery stream.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/harkers/forge-email-server --skill notification-hub-harkers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notification-hub
Source: https://github.com/harkers/forge-email-server/tree/main/forgediscord/skills/mupeng-notification-hub
Command: npx skills add https://github.com/harkers/forge-email-server --skill notification-hub-harkers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified notification management for multiple skills to reduce fatigue and ensure timely delivery based on priority.

Core Features & Use Cases

  • Centralized collection of events from all skills and delivery by priority
  • Priority routing to Discord DM, heartbeat, and daily reports
  • Duplicate prevention and memory history to avoid repeated notifications
  • Flexible activation via natural language prompts to adjust notification behavior

Quick Start

Configure sources and channels, then activate the notification-hub to start aggregating and routing alerts.

Frequently Asked Questions about notification-hub

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

FAQPage Schema
How do I consolidate multiple skill notifications into a single Discord delivery stream?

You can consolidate multiple skill notifications into a single Discord stream by aggregating diverse events and routing them by priority. Urgent alerts are delivered via Discord DM, while less critical events are bundled into heartbeats or daily summaries to reduce noise.

What is the best way to prevent duplicate alerts in an automated event-processing workflow?

The best way to prevent duplicate alerts in event-processing is to apply deterministic routing and deduplication rules. By tracking sent notifications and persisting history, the system ensures repeated events are identified and suppressed before delivery.

How does priority-based notification routing work for urgent, important, and info classifications?

Priority-based notification routing works by classifying events into urgent, important, and info categories. Urgent alerts trigger immediate Discord DMs, important events are bundled into heartbeats, and info events are compiled into daily summary reports.

Can I adjust notification behavior and routing rules using natural language prompts?

Yes, you can adjust notification behavior using natural language prompts. This flexible activation allows you to modify how alerts are aggregated, prioritized, and routed without manual configuration changes.

How do I configure notification channels and heartbeats for centralized alert management?

To configure notification channels and heartbeats for alert management, you set up your diverse event sources and delivery destinations. Once configured, the hub automatically aggregates events and routes them by priority to the appropriate channels.

Why am I receiving notification fatigue from multiple monitoring skills and how do I reduce it?

You receive notification fatigue from multiple monitoring skills due to unmanaged, overlapping alert streams. You can reduce it by centralizing collection and applying deduplication rules to consolidate events into a low-noise delivery stream prioritized by urgency.