configure-notifications

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

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/byonk19-svg/rt-scheduler --skill configure-notifications-byonk19-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-notifications
Source: https://github.com/byonk19-svg/rt-scheduler/tree/main/.codex/skills/configure-notifications
Command: npx skills add https://github.com/byonk19-svg/rt-scheduler --skill configure-notifications-byonk19-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure OMX notifications from a single entry point to unify multi-platform setup and reduce manual configuration drift.

Core Features & Use Cases

  • Centralized management for native integrations (Discord, Telegram, Slack) and generic webhook/CLI gateways
  • Guidance for inspecting current state, applying per-platform settings, and validating changes
  • Supports OpenClaw-based routing and advanced gates when OMX_OPENCLAW is enabled for extended workflows

Quick Start

Run the configure-notifications skill to initialize and manage OMX notification settings across supported platforms.

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?

Configuring OMX notifications across platforms is centralized from a single entry point to unify setup and reduce manual configuration drift. It applies settings across native integrations like Discord, Telegram, and Slack, alongside generic webhook and CLI gateways.

What is the best way to inspect and update notification settings for Telegram and Discord?

The best way to update notification settings is through interactive steps that inspect the current state, apply per-platform configurations, and validate changes. This ensures Telegram and Discord settings are correctly applied without drift.

Do I need OpenClaw enabled to manage webhook routing for OMX notifications?

OpenClaw is not required for basic webhook routing but is needed for advanced flows. You must enable the OMX_OPENCLAW environment gate to use OpenClaw-based routing and gate controls for extended notification workflows.

Can I use generic CLI gateways to send OMX notifications instead of native platform integrations?

Yes, you can use generic webhook and CLI gateways to send OMX notifications. The configuration process supports these gateways alongside native platform integrations to provide flexible routing options.

How do I validate that my Slack notification configuration is working correctly?

You validate your Slack notification configuration by running smoke tests after applying updates. This interactive validation step confirms that your per-platform settings are functioning correctly.

Why does my OMX notification setup require environment gates like OMX_OPENCLAW_COMMAND?

Environment gates like OMX_OPENCLAW_COMMAND are required to govern advanced notification flows securely. They control when OpenClaw-based routing and extended gateways are activated during your configuration process.