From notify-telegram
Send a notification message to the user via Telegram. Use when the user has asked to receive updates via Telegram, or when explicitly asked to send a Telegram message. Also use /notify-telegram:notify setup to configure credentials.
npx claudepluginhub mararn1618/mararn1618-claude-marketplace --plugin notify-telegramThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Compresses source documents into lossless, LLM-optimized distillates preserving all facts and relationships. Use for 'distill documents' or 'create distillate' requests.
Send one-way notification messages to the user via the Telegram Bot API.
/notify-telegram:notifyIf the config file ~/.claude/telegram.env does not exist, or the user says "setup" or "configure", guide them through setup:
Tell the user:
To create a Telegram bot:
- Open Telegram and search for
@BotFather- Send
/newbotand follow the prompts- You'll receive a bot token like
123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11- Start a conversation with your new bot (search for it and press "Start") — this is required before the bot can message you
If the user doesn't know their chat ID, help them find it:
Send any message to your bot first (e.g. "hello"), then I'll look it up.
Then run:
curl -s "https://api.telegram.org/bot${TOKEN}/getUpdates" | python3 -c "import sys,json; updates=json.load(sys.stdin)['result']; print(updates[-1]['message']['chat']['id'] if updates else 'No messages found - please send a message to your bot first')"
Replace ${TOKEN} with the token the user provided.
Create the config file:
cat > ~/.claude/telegram.env << 'EOF'
TELEGRAM_BOT_TOKEN=<token>
TELEGRAM_CHAT_ID=<chat_id>
EOF
chmod 600 ~/.claude/telegram.env
Send a test message to verify the setup works. Use the sending instructions below. The test message should be:
Setup complete! Telegram notifications are working.
After successful test, tell the user they can now ask for Telegram notifications in any session.
source ~/.claude/telegram.env
If the file doesn't exist, tell the user to run /notify-telegram:notify setup first.
Use this exact pattern:
source ~/.claude/telegram.env && curl -s -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage" \
-H 'Content-Type: application/json' \
-d "$(python3 -c "
import json, sys
msg = '''MESSAGE_TEXT_HERE'''
print(json.dumps({
'chat_id': '${TELEGRAM_CHAT_ID}',
'text': msg,
'parse_mode': 'HTML'
}))
")"
Replace MESSAGE_TEXT_HERE with the actual message. Using python3 for JSON encoding ensures proper escaping of special characters, quotes, and newlines.
Telegram has a 4096 character limit. If your message is longer, split it into multiple sends. Prefer summarizing over splitting.
The API returns JSON. Check that "ok": true is in the response. If not, show the error to the user.
<b>bold</b> for emphasis on key terms<code>inline code</code> for file paths, commands, variable names<pre>code block</pre> for multi-line code output<i>italic</i> for secondary information<u> underline tags\n in the message)Task completion:
Done! Refactored the auth module.
3 files changed:
- src/auth/login.ts
- src/auth/session.ts
- src/auth/types.ts
All 42 tests passing.
Error notification:
Build failed in CI.
The test UserService.create is failing:
Expected 201 but got 400
Looks like the validation schema changed. I can investigate if you want.
Progress update:
Migration progress: 15/23 endpoints converted.
Currently working on /api/v2/orders.
No blockers so far.
~/.claude/telegram.env is missing: tell user to run setup"ok": false: show the error message from the API response to the user