configure-notifications

Configure OMX notifications for Discord, Telegram, Slack, and custom webhook or CLI gateways.

Updated Feb 1, 2024
One-click install
npx skills add https://github.com/ogiboy/portfolio-app --skill configure-notifications-ogiboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-notifications
Source: https://github.com/ogiboy/portfolio-app/tree/main/.codex/skills/configure-notifications
Command: npx skills add https://github.com/ogiboy/portfolio-app --skill configure-notifications-ogiboy

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

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 for Discord?

Run the configure-notifications flow and choose Discord from the main menu, then provide either a webhook URL or bot credentials. The Skill writes the values under notifications.discord or notifications["discord-bot"] in ~/.codex/.omx-config.json.

How do I set up Telegram or Slack notifications in OMX?

Select Telegram or Slack from the configuration menu and supply a bot token plus chat id for Telegram, or an incoming webhook URL for Slack. Values are written to notifications.telegram or notifications.slack respectively.

What is the difference between custom_webhook_command and custom_cli_command?

custom_webhook_command sends HTTP requests to a URL with configurable method, headers, and events, while custom_cli_command executes a local command template supporting placeholders like {{event}}, {{sessionId}}, and {{projectPath}}. Both are generic aliases ignored when an explicit notifications.openclaw config exists.

Does OMX support routing notifications through clawdbot agent?

Yes, a command gateway can invoke clawdbot agent with delivery to Discord using --reply-to 'channel:CHANNEL_ID'. Set the gateway timeout to 120000 ms, require OMX_OPENCLAW=1 and OMX_OPENCLAW_COMMAND=1, and log output to a .jsonl file for troubleshooting.

How do I disable all OMX notifications?

Choose the disable option in the menu or run jq '.notifications.enabled = false' on ~/.codex/.omx-config.json. This turns off every platform and gateway without deleting their stored settings.

Why are my custom webhook settings being ignored by OMX?

OMX applies deterministic precedence: an explicit notifications.openclaw configuration wins when present and valid, so generic aliases like custom_webhook_command are ignored with a warning. Remove or adjust the openclaw block to re-enable the aliases.