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.
Install
$ agentstack add skill-alberduris-skills-telegram-notify ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-alberduris-skills-telegram-notify) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Telegram Bot API skill. All commands go through bash /telegram.sh .
[!COMMANDS]
a) bash /telegram.sh send — send a message to the configured chat immediately. b) bash /telegram.sh schedule — schedule a message for later delivery via Cloudflare Worker. c) bash /telegram.sh scheduled — list all pending scheduled messages. d) bash /telegram.sh cancel — cancel a scheduled message by ID. e) bash /telegram.sh me — get bot info; useful for debugging credential issues.
[!DATETIME FORMATS for schedule]
The `` argument accepts multiple formats. Always quote it if it contains spaces.
+30m,+2h,+1d,+2h30m— relative from now15: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_TOKENandTELEGRAM_CHAT_IDas environment variables (or in.env/.env.local). - schedule, scheduled, cancel: Additionally require
TELEGRAM_WORKER_URLandTELEGRAM_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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: alberduris
- Source: alberduris/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.