What problem does it solve?
This Skill removes the complexity of setting up and maintaining OMX notification delivery, whether you need a native platform integration, a generic command gateway, or cross-cutting behavior like verbosity and reply handling.
Core Features & Use Cases
- Native platform setup: Configure Discord, Telegram, and Slack through their dedicated notification keys.
- Extensible delivery paths: Enable custom webhook commands or custom CLI commands for flexible event routing.
- OpenClaw compatibility: Support explicit OpenClaw-backed notification schemas and enforce precedence over generic aliases when both exist.
- Operational controls: Manage event triggers, idle cooldowns, verbosity levels, profiles, and reply listener behavior.
- Use case: A developer can route session-end alerts to Slack, keep session-idle noise low, and preserve a reply-scoped status probe for authorized Discord responders.
Quick Start
Inspect the existing notification settings and configure the requested channels in ~/.codex/.omx-config.json, then confirm the final state and any precedence rules that apply.