configure-notifications

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

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/hotaq/Sprite_harmess --skill configure-notifications-hotaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-notifications
Source: https://github.com/hotaq/Sprite_harmess/tree/main/.codex/skills/configure-notifications
Command: npx skills add https://github.com/hotaq/Sprite_harmess --skill configure-notifications-hotaq

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

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 send alerts to Discord, Slack, and Telegram?

To configure OMX notifications, edit the ~/.codex/.omx-config.json file to specify your Discord, Slack, and Telegram keys. You can route session-end alerts and other events directly through these native platform integrations.

Can I use a custom webhook or CLI command for OMX event routing?

Yes, you can enable custom webhook commands or custom CLI commands for flexible OMX event routing. This allows you to route notifications to platforms outside the native Discord, Slack, and Telegram integrations.

How does OpenClaw-backed notification routing handle precedence over generic aliases?

OpenClaw-backed notification schemas enforce precedence over generic aliases when both exist. This ensures explicit OpenClaw routing takes priority during event delivery configuration and maintenance.

How do I reduce notification noise from idle session alerts?

You can reduce idle session alert noise by adjusting the idle cooldown settings and verbosity levels. These operational controls are configured within your ~/.codex/.omx-config.json file.

Why are my OMX notifications not working after updating the config file?

OMX notifications may fail due to invalid configurations in ~/.codex/.omx-config.json. You need to validate event gating, reply listener state, and run a smoke-test verification to troubleshoot the delivery issue.

What is the best way to test OMX notification delivery after setup?

The best way to test OMX notification delivery is by running a smoke-test verification. This validates your event gating, precedence handling, and reply listener state to ensure alerts are routing correctly.