notifier-add

Add a new notification channel type to the alerts pipeline.

55|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/MrSuttonmann/flightjar --skill notifier-add
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notifier-add
Source: https://github.com/MrSuttonmann/flightjar/tree/main/.claude/skills/notifier-add
Command: npx skills add https://github.com/MrSuttonmann/flightjar --skill notifier-add

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating alert channels across code, config, UI, and tests to add a new notifier type is error-prone; this skill provides a structured, multi-file pattern to extend the alerts pipeline with a new channel type safely and consistently.

Core Features & Use Cases

  • Enables adding a new channel type (Discord, Slack, Pushover, Matrix, SMTP, Signal, …) to the alerts pipeline by updating the shared enum, config store, notifier, DI wiring, UI, and test suites.
  • Provides a repeatable integration blueprint so teams can implement a new channel without breaking existing flows, including enum, IsReady logic, and test scaffolding.
  • Use case: extend alerts to a new Slack/Discord channel to notify on incidents while preserving config persistence and test coverage.

Quick Start

Implement a new notifier channel by adding an INotifier, updating the enum and config store, wiring DI, updating the Alerts UI, and adding tests.

Frequently Asked Questions about notifier-add

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

FAQPage Schema
How do I add a new notification channel to an alerts pipeline?

To add a new notification channel, you extend the alerts pipeline by updating the shared enum, config store, notifier implementation, DI wiring, UI persistence, and test suites.

Why does adding a new notifier break my existing alerts pipeline?

Adding a new notifier type often breaks existing flows because it requires coordinated updates across the enum, IsReady logic, Clean() integration, and DI registration to maintain consistency.

Does this notifier extension pattern work with Discord and Slack webhooks?

Yes, the notifier extension pattern applies to scenarios where teams need to support additional channels like Discord, Slack, Pushover, Matrix, SMTP, and Signal by updating the config store and notifier.

What is the best way to implement a new alert channel in dotnet?

The best way to implement a new alert channel is using a structured, multi-file pattern that adds an INotifier, updates the shared enum and config store, wires DI, updates the Alerts UI, and adds tests.

Can I use this approach to extend alerts without writing new tests?

No, this approach requires adding tests to satisfy functional and technical requirements, ensuring the new channel type integrates safely without breaking existing config persistence or alert flows.

When do I need to update the Clean() integration for a new notifier?

You need to update the Clean() integration whenever you add a new notification channel type, as it is a required technical step alongside enum extension, IsReady checks, and DI registration.