What problem does it solve? Setting up OMX session notifications across multiple platforms requires editing a JSON config file by hand and knowing each platform's schema. This Skill provides a single guided entry point that inspects the current configuration, collects platform credentials, and writes validated settings to ~/.codex/.omx-config.json. ## Core Features & Use Cases - Native platform setup: Configure Discord (webhook or bot), Telegram (bot token plus chat id), and Slack (incoming webhook) under their dedicated config keys. - Generic extensibility: Register custom_webhook_command or custom_cli_command gateways with templated instructions, event lists, and OpenClaw/clawdbot agent routing for dev workflows. - Cross-cutting controls: Manage verbosity levels, idle cooldown, notification profiles, the reply listener, and a one-command disable-all switch. - Use Case: A developer wants session-end and idle events from OMX delivered to a Discord channel via a clawdbot agent. The Skill writes the gateway, per-hook instructions, and timeout settings, then provides verification commands and a JSONL log inspection runbook. ## Quick Start Ask the assistant to configure OMX notifications for Discord and follow the menu to enter your webhook URL and event preferences.