configure-notifications

Configure OMX notifications for Discord, Telegram, and Slack from a single entry point.

Updated Jul 3, 2025
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill configure-notifications-andrew-t-james
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-notifications
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_codex/skills/configure-notifications
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill configure-notifications-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMX notifications across platforms are managed separately, leading to inconsistent behavior and manual setup across each integration. This skill provides a single entry point to configure native integrations (Discord, Telegram, Slack) and extensibility options (custom_webhook_command, custom_cli_command) for centralized control.

Core Features & Use Cases

  • Unified entry point for notification setup across platforms.
  • Native integrations supported: Discord, Telegram, Slack.
  • Extensibility through custom_webhook_command and custom_cli_command.
  • Removes standalone configure-skills in favor of a single, cohesive workflow.

Quick Start

Run the configure-notifications skill to initialize OMX notification settings across the enabled platforms.

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 multiple platforms?

Configure OMX notifications across multiple platforms from a single entry point. This skill manages native integrations for Discord, Telegram, and Slack, enforcing a unified schema for consistent behavior and centralized control over per-project settings.

Can I set up custom webhook commands for OMX notifications?

Yes, you can set up custom webhook commands for OMX notifications. The configuration supports extensibility hooks like custom_webhook_command and custom_cli_command, allowing you to integrate with platforms beyond the native Discord, Telegram, and Slack support.

What is the best way to manage Discord, Slack, and Telegram notifications together?

The best way to manage Discord, Slack, and Telegram notifications together is using a unified configuration schema. This approach removes standalone setup processes, providing a single cohesive workflow for centralized control and quick changes across all native integrations.

Does this notification configuration support OpenClaw compatibility options?

Yes, the notification configuration supports OpenClaw compatibility options. It uses a YAML frontmatter-driven SKILL.md to guide step-by-step configuration, ensuring the unified notifications schema aligns with OpenClaw requirements across your project settings.

Why are my separate notification integrations behaving inconsistently?

Separate notification integrations behave inconsistently because they are managed individually. Using a single entry point to configure native integrations and extensibility hooks enforces a unified schema, resolving manual setup discrepancies and standardizing behavior across platforms.

Do I need standalone configure-skills for each notification platform?

No, you do not need standalone configure-skills for each notification platform. This skill removes standalone configuration workflows in favor of a single, cohesive entry point that manages all native integrations and custom extensibility hooks together.