configure-notifications

Centralize OMX notification configuration across Discord, Telegram, Slack, and generic gateways.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/eszxcvfd/ANIZAKI --skill configure-notifications-eszxcvfd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-notifications
Source: https://github.com/eszxcvfd/ANIZAKI/tree/main/.agents/skills/configure-notifications
Command: npx skills add https://github.com/eszxcvfd/ANIZAKI --skill configure-notifications-eszxcvfd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified and centralized configuration of OMX notifications across native channels (Discord, Telegram, Slack) and generic gateways, reducing fragmentation and manual setup.

Core Features & Use Cases

  • Native integrations (first-class): Discord, Telegram, Slack enable direct, reliable alert delivery.
  • Generic extensibility integrations: custom_webhook_command and custom_cli_command expand integration options.
  • Use Case: Teams manage multi-platform alerts from a single configuration, ensuring consistent behavior and easier audits.

Quick Start

Edit the OMX configuration file to enable and tune notifications for your project and platforms.

Frequently Asked Questions about configure-notifications

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

FAQPage Schema
How do I centralize OMX notifications across Discord, Slack, and Telegram?

Centralize OMX notifications by editing a single configuration file to govern multi-platform alert delivery. This enables consistent behavior across native channels and easier audits without manual setup.

Can I use a custom webhook command for alerting?

You can configure custom webhook commands for generic gateway alerting. The configuration supports expanding integration options beyond native channels like Slack and Telegram.

What is the best way to manage versioned alert configurations for multiple platforms?

Use a centralized configuration file to manage versioned alert setups across native platforms. This approach ensures consistent behavior and reduces fragmentation across multi-platform integrations.

How does the precedence contract work for per-platform notification keys?

The precedence contract enforces safety validations across per-platform keys. This mechanism ensures reliable, ordered application of alert settings across native and generic gateway integrations.

Are safety validations enforced for custom CLI command integrations?

Safety validations are enforced across all configurations including custom CLI commands. This ensures reliable alert delivery and consistent behavior when expanding integrations via generic gateways.