configure-notifications

Configure OMX notifications for Discord, Telegram, Slack, and custom gateways.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates and streamlines OMX notification configuration across native platforms and custom gateways, reducing setup time and ensuring consistent behavior.

Core Features & Use Cases

  • Native platform integrations: Discord, Telegram, Slack
  • Generic extensibility through custom_webhook_command and custom_cli_command
  • Centralized management with deterministic precedence between explicit notifications.openclaw and generic aliases

Quick Start

Provide OMX with your preferred notification targets and confirm the unified configuration.

Frequently Asked Questions about configure-notifications

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

FAQPage Schema
How do I configure OMX notifications for Discord, Slack, and Telegram?

You can configure OMX notifications for Discord, Slack, and Telegram by updating the centralized configuration file at ~/.codex/.omx-config.json to specify your preferred native platform targets.

Can I use a custom webhook to send OMX notifications?

Yes, OMX supports generic extensibility through custom_webhook_command and custom_cli_command, allowing you to route notifications to generic webhook or CLI gateways beyond native platforms.

What is the precedence for OMX notification aliases versus explicit settings?

OMX applies deterministic precedence between explicit notifications.openclaw settings and generic aliases, ensuring consistent notification routing behavior across configured platforms and custom gateways.

Where does OMX store unified notification configurations?

OMX stores unified notification configurations in the ~/.codex/.omx-config.json file, centralizing management for native platforms and custom webhook or CLI gateways.

Does OMX support generic CLI gateways for notification delivery?

Yes, OMX supports generic CLI gateways through the custom_cli_command configuration, enabling centralized notification delivery alongside native Discord, Telegram, and Slack integrations.

What is the best way to consolidate notifications across multiple platforms in OMX?

The best way to consolidate notifications is using unified OMX configuration, which streamlines setup across native platforms and custom gateways while ensuring deterministic precedence and consistent behavior.