configure-notifications

Configure Telegram, Discord, and Slack notification integrations for session events.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/OliverOuyang/shuhe-work-skills --skill configure-notifications-oliverouyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-notifications
Source: https://github.com/OliverOuyang/shuhe-work-skills/tree/main/skills/configure-notifications
Command: npx skills add https://github.com/OliverOuyang/shuhe-work-skills --skill configure-notifications-oliverouyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help users quickly configure and validate notification integrations so OMC/Claude Code can send session and event alerts to Telegram, Discord, and Slack without manual JSON editing or guesswork.

Core Features & Use Cases

  • Interactive Setup Wizard: Guided prompts to collect bot tokens, chat IDs, webhook URLs, mention targets, and optional display names.
  • Validation and Testing: Pattern checks for tokens/URLs, live test messages to verify delivery, and error explanations for common API failures.
  • Config Management & Migration: Merge settings into ~/.claude/.omc-config.json, support environment variable alternatives, per-event templates, and migration from legacy OpenClaw configs.
  • Use Case: Configure Telegram and Discord to receive session-end and input-needed alerts for long-running automated analyses and CI-like background tasks.

Quick Start

Use the configure-notifications skill to walk through adding a Telegram bot token and chat ID and send a test notification.

Frequently Asked Questions about configure-notifications

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Telegram bot alerts for long-running automated sessions?

Configure Telegram bot alerts by running an interactive setup wizard that collects your bot token and chat ID, validates the credentials, and merges them into ~/.claude/.omc-config.json to send session-start, session-end, and input-needed event notifications.

Can I send automated event notifications to both Discord and Slack without editing JSON files manually?

Yes, you can send notifications to Discord and Slack without manual JSON editing by using guided prompts to collect webhook URLs and bot tokens, which are then automatically validated and merged into the ~/.claude/.omc-config.json configuration file.

Does the notification configuration support environment variable overrides for bot tokens and webhook URLs?

The notification configuration supports environment variable overrides for credentials like bot tokens, chat IDs, and webhook URLs, allowing you to bypass the interactive prompts and manage sensitive session alert settings directly through your system environment.

What's the best way to test if my Discord webhook is correctly configured for session alerts?

The best way to test your Discord webhook is to use the built-in validation feature, which performs pattern checks on the webhook URL and optionally sends a live test message to verify delivery and explain any common API failures before enabling session alerts.

Why are my Slack webhook notifications not being delivered after updating the config file?

Slack webhook notifications may fail delivery if the URL pattern is invalid or API credentials are rejected; the setup wizard provides error explanations for common API failures and performs live test messages to help diagnose the delivery issue.

Can I use custom per-event templates for Telegram and Slack session notifications?

Yes, you can use custom per-event templates for Telegram and Slack notifications, allowing you to define specific message formats for session-start, session-end, input-needed, and persistent session events within the merged configuration.