configure-telegram_skill

This skill configures Telegram notifications for OMC by guiding setup and saving a usable config for alerts on session events.
  • TypeScript

6.8k

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-telegram

  • SKILL.md6.7 KB

Overview

This skill guides you through configuring Telegram bot notifications for session events using natural language prompts. It interactively collects your bot token, chat ID, preferred message format, and which events should trigger notifications, then writes or updates the OMC configuration. A built-in test step verifies the setup.

How this skill works

The skill detects any existing configuration and shows current Telegram settings, then asks targeted questions to collect or update the bot token, chat ID, parse mode, and event selections. It validates token and chat ID formats, merges the new settings into ~/.claude/.omc-config.json (or uses environment variables), and optionally sends a test message to confirm the connection. If a test fails, the skill reports common errors and suggests troubleshooting steps.

When to use it

  • You want push notifications for session end, long-running tasks, or prompts for input.
  • Setting up alerts for a personal or group Telegram chat when an agent requires attention.
  • You prefer a guided, interactive setup rather than manual JSON editing.
  • You want to verify Telegram connectivity immediately with a test message.
  • You need to toggle which events trigger notifications without editing files manually.

Best practices

  • Have a Telegram bot token from @BotFather and send /start to the bot before collecting chat ID.
  • Validate the token format (digits:alphanumeric) and the chat ID (numeric, negative for groups) when prompted.
  • Prefer Markdown parse mode for readable messages unless you need HTML formatting for advanced styling.
  • Use the test notification step to confirm credentials and chat reachability before relying on alerts.
  • Keep a backup of OMC configuration or use environment variables (OMC_TELEGRAM_BOT_TOKEN and OMC_TELEGRAM_CHAT_ID) if you prefer not to store tokens in files.

Example use cases

  • Notify a developer when a long-running code-generation session requires user input.
  • Alert a team channel when a scheduled background task completes or fails.
  • Receive a confirmation in your personal chat when a persistent session starts or ends.
  • Quickly reconfigure notifications across environments by exporting OMC_TELEGRAM_* environment variables.
  • Disable specific events (e.g., session-start) to reduce noise while keeping critical alerts enabled.

FAQ

The token must match digits:alphanumeric (example: 123456789:ABCdefGHIjklMNOpqrsTUVwxyz). If it fails validation, recheck the token from @BotFather and paste it again.

Why did the test notification fail with 401 or 400?

401 Unauthorized means the bot token is invalid. 400 Bad Request: chat not found means the chat ID is wrong or you haven’t sent /start to the bot. Recheck both and run the test again.

Can I skip the wizard and set values manually?

Yes. Export OMC_TELEGRAM_BOT_TOKEN and OMC_TELEGRAM_CHAT_ID in your shell profile; the system auto-detects these variables and skips the wizard.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
configure-telegram skill by yeachan-heo/oh-my-claudecode | VeilStrat