configure-notifications

Configure OMX notifications across Discord, Telegram, Slack, and generic gateways.

1|Updated Mar 17, 2025
One-click install
npx skills add https://github.com/ozby/node-pubsub --skill configure-notifications-ozby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-notifications
Source: https://github.com/ozby/node-pubsub/tree/main/.codex/skills/configure-notifications
Command: npx skills add https://github.com/ozby/node-pubsub --skill configure-notifications-ozby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMX notifications are often configured separately across platforms, tools, and gateways, leading to inconsistency and errors. This skill provides a unified entry point to configure native integrations (Discord, Telegram, Slack) and generic gateways, ensuring a single source of truth for notification settings.

Core Features & Use Cases

  • Centralized configuration for native platforms and generic command/webhook gateways.
  • Supports per-platform setup (Discord, Telegram, Slack) and OpenClaw-based workflows with deterministic behavior and sensible defaults.
  • Defines a compatibility precedence model to prioritize explicit runtime configuration while enabling smooth upgrades and audits.

Quick Start

Use the OMX notifications configure workflow to initialize and adjust your notification settings across platforms and gateways.

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

You can configure OMX notifications centrally by using a unified entry point that manages native integrations for Discord, Telegram, and Slack, ensuring consistent settings and a single source of truth across platforms.

What is the best way to unify fragmented notification settings across multiple platforms?

Unifying fragmented notification settings involves using a centralized configuration workflow that applies a compatibility precedence model, prioritizing explicit runtime configuration while maintaining deterministic behavior and safe defaults across gateways.

Can I use generic webhooks to route OMX notifications instead of native platform integrations?

Yes, you can route OMX notifications through generic command and webhook gateways alongside native integrations, with the system applying explicit compatibility precedence to prioritize runtime configuration during setup.

How do I safely disable or modify active notification channels without losing existing configurations?

You can safely disable or modify active notification channels through a guided workflow that maintains security and auditability, applying compatibility precedence to ensure smooth upgrades and deterministic behavior.

Does OpenClaw support centralized OMX notification workflows?

Yes, OpenClaw supports centralized OMX notification workflows by providing deterministic behavior, sensible defaults, and a compatibility precedence model for managing native platforms and generic gateways.

Why do my separate OMX notification configurations cause inconsistencies across platforms?

Separate OMX notification configurations cause inconsistencies because they lack a single source of truth, a problem solved by applying a centralized configuration workflow with explicit compatibility precedence and safe defaults.