- Home
- Skills
- Yeachan Heo
- Oh My Claudecode
- Configure Notifications
configure-notifications_skill
- TypeScript
9.3k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill yeachan-heo/oh-my-claudecode --skill configure-notifications- SKILL.md35.2 KB
Overview
This skill configures notification integrations (Telegram, Discord, Slack) for the OMC agent system using natural language prompts. It guides the user through interactive steps, validates inputs, writes merged settings to ~/.claude/.omc-config.json, and can optionally send a test notification. The skill supports webhook- and bot-based flows and environment variable alternatives for automation.
How this skill works
The skill inspects existing configuration and asks targeted questions to collect provider-specific credentials and preferences (bot tokens, chat/channel IDs, webhook URLs, parse modes, and event triggers). It validates formats, merges changes into the JSON config file, and offers an immediate test call to verify delivery. It also provides environment-variable options so users can skip the wizard.
When to use it
- Set up delivery of session lifecycle events (end/start/continuing)
- Get instant alerts when a session requires user input
- Switch or reconfigure notification providers (Telegram, Discord, Slack)
- Automate notification setup in CI or new developer environments
- Verify connectivity and permissions for chat integrations
Best practices
- Confirm you or the bot have sent an initial message to the target chat (Telegram) to avoid “chat not found” errors
- Prefer webhooks for Discord when you only need simple posting (no bot permissions required)
- Validate tokens and IDs with the provided formats before saving to avoid failed tests
- Limit mentions to reduce noise; prefer role/user IDs for targeted pings
- Store sensitive values in environment variables (OMC_TELEGRAM_BOT_TOKEN, OMC_TELEGRAM_CHAT_ID, etc.) when automating
Example use cases
- Configure Telegram to receive a message when long-running code sessions complete
- Add a Discord webhook so a team channel is notified when a session needs input
- Set a Slack incoming webhook to post session start/end summaries to an ops channel
- Switch from Discord bot to webhook for simpler permissions
- Provision notifications as part of a developer machine setup using env vars
FAQ
401 usually means the bot token is invalid; double-check the format (digits:alphanumeric) or recreate the bot via @BotFather.
How do I get a Discord channel or user ID?
Enable Developer Mode in Discord, then right-click the channel, user, or role and choose Copy ID; use the ID in the configuration prompts.
Can I skip the wizard and use environment variables?
Yes. Export provider-specific vars (for example OMC_TELEGRAM_BOT_TOKEN and OMC_TELEGRAM_CHAT_ID) and the system will detect them without writing .omc-config.json.