How do I install the Telegram Notify skill?

Run npx skillmds@latest add alberduris/telegram-notify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Telegram Notify safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Telegram Notify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Telegram Notify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Telegram Notify?

alberduris (@alberduris) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Telegram Notify by alberduris — Agent Skill

Name: Telegram Notify
Author: alberduris

Telegram Notify

Send notifications via Telegram. Use when the user asks to notify, alert, message, or ping — or when a long-running task completes and the user previously asked to be notified. Can also schedule messages for later delivery.

alberduris 6f041cc 2 files · 12.8 KB Updated Sep 17, 2026

File contents

Telegram Bot API skill. All commands go through bash <base_directory>/telegram.sh <command>.

[!COMMANDS]

a) bash <base_directory>/telegram.sh send <text> — send a message to the configured chat immediately. b) bash <base_directory>/telegram.sh schedule <datetime> <text> — schedule a message for later delivery via Cloudflare Worker. c) bash <base_directory>/telegram.sh scheduled — list all pending scheduled messages. d) bash <base_directory>/telegram.sh cancel <id> — cancel a scheduled message by ID. e) bash <base_directory>/telegram.sh me — get bot info; useful for debugging credential issues.

[!DATETIME FORMATS for schedule]

The <datetime> argument accepts multiple formats. Always quote it if it contains spaces.

+30m, +2h, +1d, +2h30m — relative from now
15:00 — today at that time (local tz); if already passed, assumes tomorrow
"tomorrow 09:00" or "mañana 09:00" — tomorrow at that time (local tz)
"today 15:00" or "hoy 15:00" — today at that time (local tz)
"2026-04-07 09:00" — date + time (local tz)
2026-04-07T09:00:00Z — ISO 8601 (UTC)

[!CREDENTIALS]

send, me: Require TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID as environment variables (or in .env / .env.local).
schedule, scheduled, cancel: Additionally require TELEGRAM_WORKER_URL and TELEGRAM_API_TOKEN (the Cloudflare Worker endpoint and its auth token).

If missing, tell the user to check the README for setup instructions.

[!GUIDELINES]

This is instant messaging, not a report. Write the way you'd write a quick Telegram message to a coworker: one or two short sentences, no more. No markdown, no formatting, no bullet points, no tables, no code blocks, no headers, no bold, no italic. Just plain text. If you're tempted to send more than 2-3 lines, you're sending too much. The user will read this on their phone and a wall of text is a terrible experience. Summarize aggressively. The point is to get the user back to the session, not to deliver a full report over Telegram.
Never send credentials, secrets, or sensitive data through Telegram unless the user explicitly asks for it.
Scheduled messages have ~5 min granularity (the worker checks the queue every 5 minutes). Don't promise exact-to-the-second delivery.

---name: telegram-notifydescription: Send notifications via Telegram. Use when the user asks to notify, alert, message, or ping — or when a long-running task completes and the user previously asked to be notified. Can also schedule messages for later delivery.---Telegram Bot API skill. All commands go through `bash <base_directory>/telegram.sh <command>`.[!COMMANDS]a) `bash <base_directory>/telegram.sh send <text>` — send a message to the configured chat immediately.b) `bash <base_directory>/telegram.sh schedule <datetime> <text>` — schedule a message for later delivery via Cloudflare Worker.c) `bash <base_directory>/telegram.sh scheduled` — list all pending scheduled messages.d) `bash <base_directory>/telegram.sh cancel <id>` — cancel a scheduled message by ID.e) `bash <base_directory>/telegram.sh me` — get bot info; useful for debugging credential issues.[!DATETIME FORMATS for schedule]The `<datetime>` argument accepts multiple formats. Always quote it if it contains spaces.- `+30m`, `+2h`, `+1d`, `+2h30m` — relative from now- `15:00` — today at that time (local tz); if already passed, assumes tomorrow- `"tomorrow 09:00"` or `"mañana 09:00"` — tomorrow at that time (local tz)- `"today 15:00"` or `"hoy 15:00"` — today at that time (local tz)- `"2026-04-07 09:00"` — date + time (local tz)- `2026-04-07T09:00:00Z` — ISO 8601 (UTC)[!CREDENTIALS]- **send, me**: Require `TELEGRAM_BOT_TOKEN` and `TELEGRAM_CHAT_ID` as environment variables (or in `.env` / `.env.local`).- **schedule, scheduled, cancel**: Additionally require `TELEGRAM_WORKER_URL` and `TELEGRAM_API_TOKEN` (the Cloudflare Worker endpoint and its auth token).If missing, tell the user to check the README for setup instructions.[!GUIDELINES]- This is instant messaging, not a report. Write the way you'd write a quick Telegram message to a coworker: one or two short sentences, no more. No markdown, no formatting, no bullet points, no tables, no code blocks, no headers, no bold, no italic. Just plain text. If you're tempted to send more than 2-3 lines, you're sending too much. The user will read this on their phone and a wall of text is a terrible experience. Summarize aggressively. The point is to get the user back to the session, not to deliver a full report over Telegram.- Never send credentials, secrets, or sensitive data through Telegram unless the user explicitly asks for it.- Scheduled messages have ~5 min granularity (the worker checks the queue every 5 minutes). Don't promise exact-to-the-second delivery.

Frequently asked questions