configure-notifications

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

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Linnanli/xClaw --skill configure-notifications-linnanli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-notifications
Source: https://github.com/Linnanli/xClaw/tree/main/.codex/skills/configure-notifications
Command: npx skills add https://github.com/Linnanli/xClaw --skill configure-notifications-linnanli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidate and streamline the configuration of OMX notifications across native platforms and generic gateways to ensure consistent, auditable alerting.

Core Features & Use Cases

  • Centralized configuration for native integrations (Discord, Telegram, Slack) and extensible gateways (custom_webhook_command, custom_cli_command)
  • Safe, gated activation of OpenClaw-backed dispatch with environment controls to prevent accidental exposure or misrouting
  • Quick validation and testing workflows to verify notification delivery across platforms and integration points

Quick Start

Configure OMX notifications by following the guided prompts to enable Discord, Telegram, Slack, and any custom webhook or CLI gateways.

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 in one place?

Validate OMX notification delivery by using the built-in testing workflows to verify that alerts route correctly to Discord, Telegram, Slack, and custom gateways before relying on them.

Can I route OMX alerts to a custom webhook command or CLI tool?

Yes, OMX supports generic extensibility through custom_webhook_command and custom_cli_command gateways, allowing you to route alerts to custom endpoints or execute local CLI commands.

What environment variables are required to activate OpenClaw-backed dispatch for OMX alerts?

Activating OpenClaw-backed dispatch requires setting OMX_OPENCLAW=1, and enabling command gateways requires OMX_OPENCLAW_COMMAND=1, with an optional OMX_OPENCLAW_COMMAND_TIMEOUT_MS override.

How do I test and validate OMX notification delivery across multiple platforms?

Validate OMX notification delivery by using the built-in testing workflows to verify that alerts route correctly to Discord, Telegram, Slack, and custom gateways before relying on them.