configure-notifications

Configure OMX notifications across Discord, Telegram, Slack, and CLI/webhook gateways.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/RJJJJ/project2 --skill configure-notifications-rjjjj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-notifications
Source: https://github.com/RJJJJ/project2/tree/main/.codex/skills/configure-notifications
Command: npx skills add https://github.com/RJJJJ/project2 --skill configure-notifications-rjjjj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and simplifies configuring OMX notifications across native platforms and generic gateways, reducing setup time and misconfigurations.

Core Features & Use Cases

  • Native integrations (first-class) for Discord, Telegram, and Slack
  • Generic extensibility via custom_webhook_command and custom_cli_command
  • Step-by-step guidance to inspect, configure, test, and verify notification flows across OpenClaw, gateways, and local vs cloud modes

Quick Start

Configure OMX notifications by running the guided setup and follow the prompts in the main menu.

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 across multiple platforms like Discord and Slack?

OMX notifications can be configured across Discord, Slack, and Telegram using a unified guided setup. It centralizes native platform integrations and provides step-by-step prompts to simplify setup and reduce misconfigurations.

Can I set up custom webhook commands for OMX notifications?

Yes, custom webhook commands can be set up for OMX notifications. The system supports generic extensibility through custom_webhook_command and custom_cli_command gateways alongside its native platform integrations.

What is the best way to verify my notification configuration is deployment ready?

The best way to verify notification readiness is using the provided guided smoke-test workflow. It inspects current state, enforces compatibility rules, and checks cross-cutting settings to ensure your deployment is correctly configured.

How does OMX handle precedence between legacy openclaw and notification aliases?

OMX enforces specific compatibility rules to manage precedence between legacy openclaw configurations and newer aliases. This ensures that notification routing follows the correct priority during local and cloud deployments.

Why are my Telegram notifications not working after the initial setup?

Telegram notifications may not work due to incorrect cross-cutting settings or failing compatibility rules. Use the inspection step to check current state and the guided smoke-test workflow to identify configuration mismatches.