configure-notifications

Facilitates onboarding of employees, contractors, and visitors with automated workflows and customizable forms.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMX notifications are dispersed across multiple channels; this skill provides a unified entry point to configure and manage OMX notifications across native platforms and generic gateways.

Core Features & Use Cases

  • Native integrations (Discord, Telegram, Slack) are configured as first-class platforms
  • Generic extensibility via custom_webhook_command and custom_cli_command gateways
  • OpenClaw-backed dispatch and multi-step activation flow with safety checks and configuration persistence

Quick Start

Begin by configuring native platforms and generic gateways through the guided prompts and then review or edit the OMX config at ~/.codex/.omx-config.json.

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 across Discord, Slack, and Telegram in one place?

OMX notifications can be centralized by using a guided workflow to configure native platforms like Discord, Slack, and Telegram, unifying management settings in a single configuration file.

Can I set up custom webhook or CLI gateways for OMX notifications?

Yes, OMX notifications support generic extensibility by configuring custom webhook commands and custom CLI command gateways alongside native platform integrations through guided prompts.

Where are OMX notification settings persisted after configuration?

OMX notification settings are persisted in the OMX config file located at ~/.codex/.omx-config.json, which can be reviewed or edited after completing the guided setup process.

Does configuring OMX notifications include safety checks for the dispatch flow?

Yes, the OMX notification configuration process utilizes an OpenClaw-backed dispatch with a multi-step activation flow that includes built-in safety checks and configuration validation.

What is the best way to unify dispersed notification channels for OMX?

The best way to unify dispersed OMX notification channels is through a centralized configuration entry point that manages both native integrations and generic gateway settings with validation steps.

Do I need specific dependencies to manage OMX notification settings?

No external dependencies are required to manage OMX notification settings, as the skill operates standalone to update the OMX config file at ~/.codex/.omx-config.json with safety checks.