skills.rest
wmasfoe
wmasfoeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

configure-notifications

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

Updated Apr 23, 2026
Search Tags:#configuration#notifications#discord#slack#webhook#telegram#omx
One-click install
npx skills add https://github.com/wmasfoe/notch-pet --skill configure-notifications-wmasfoe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: configure-notifications
Source: https://github.com/wmasfoe/notch-pet/tree/main/.codex/skills/configure-notifications
Command: npx skills add https://github.com/wmasfoe/notch-pet --skill configure-notifications-wmasfoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified and centralized configuration for OMX notifications across native platforms and custom gateways, solving fragmentation and inconsistent alert routing.

Core Features & Use Cases

  • Native integrations (Discord, Telegram, Slack) as first-class channels
  • Generic extensibility through custom_webhook_command and custom_cli_command
  • OpenClaw-compatible routing with a clear precedence contract for overrides
  • Scriptable configuration via a JSON file located at ~/.codex/.omx-config.json

Quick Start

Run the configure-notifications workflow to choose platforms and customize 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 to route alerts to Discord, Telegram, and Slack?▼

Configure OMX notifications by running the setup workflow to select native Discord, Telegram, and Slack channels. It standardizes alert delivery by enforcing a unified config schema stored at ~/.codex/.omx-config.json, enabling centralized routing control.

What is the best way to standardize fragmented alert routing across custom webhooks?▼

Standardize fragmented alert routing by using a unified precedence model that resolves conflicts across native platforms and custom gateways. This configuration approach centralizes settings in a JSON file, ensuring consistent delivery through custom_webhook_command or custom_cli_command paths.

Can I use a custom webhook command for OMX notifications alongside native Slack channels?▼

Yes, you can use a custom webhook command alongside native Slack channels. The configuration supports generic extensibility through custom_webhook_command and custom_cli_command gateways while treating Discord, Telegram, and Slack as first-class native integration channels.

How does the OpenClaw integration precedence model resolve notification routing conflicts?▼

The OpenClaw integration precedence model resolves routing conflicts by enforcing a unified configuration schema with nested settings for per-channel control. This contract ensures overrides apply predictably across native platforms and custom gateways.

Where are centralized OMX notification settings stored for per-channel control?▼

Centralized OMX notification settings are stored at ~/.codex/.omx-config.json. This JSON file enforces a unified config schema and supports nested settings, allowing granular per-channel control over native platforms and custom gateway routing.

Related Skills

Explore More Software Engineering Skills→
KYRIE66nbKYRIE66nb

configure-slack

Guide Slack webhook setup for OMX notifications and write settings to ~/.codex/.omx-config.json.

Community
Intermediate
hotaqhotaq

configure-notifications

Configure OMX notification delivery across Discord, Telegram, Slack, and custom channels.

Community
Advanced
SaidabbosSaidabbos

telegram-notifications

Automates Telegram bot notifications for Golden Touch booking order lifecycle events.

Community
Intermediate
remiconnessonremiconnesson

chat-sdk

Build cross-platform chat bots with a unified SDK for multiple platforms.

Community
Advanced