alexskuznetsov/claude-skill-telegram
Overview
This skill sends immediate messages and schedules cloud-based reminders to Telegram using a Convex backend. It supports one-off timestamp scheduling, recurring reminders, attachments (as documents), viewing and canceling pending jobs, and message history. The system runs 24/7 in Convex Cloud so you don’t manage infrastructure.
How this skill works
Client scripts accept commands to send now or schedule messages with a natural-language time expression. Scheduled jobs are stored and executed by Convex, which triggers the Telegram Bot API to deliver text or document attachments to the target user. Timezone handling is done on the client side; Convex stores UTC and executes jobs with minute-level granularity.
When to use it
- Send a quick notification or alert to yourself or a user via Telegram
- Schedule a one-off reminder for a future date and time
- Create recurring reminders (daily/weekly) for routine tasks
- Attach documents (up to 50MB) and deliver them at a scheduled time
- Audit or review sent reminders using message history and list/cancel utilities
Best practices
- Always start a chat with your bot in Telegram (press Start) before sending messages
- Provide the bot token, numeric user ID, and Convex deploy key during setup to avoid runtime errors
- Keep attachments under 50MB and send as documents, not inline images
- Respect rate limits (about 20 messages/minute per user) and batch notifications when possible
- Cancel and reschedule rather than attempt to edit delivered messages
Example use cases
- Send a setup confirmation or test alert immediately after deployment
- Schedule a meeting reminder with a PDF agenda to arrive 30 minutes before start
- Create daily medication or habit reminders that run every morning
- Deliver end-of-day summaries or reports as documents to a personal Telegram chat
- List pending scheduled reminders and cancel any outdated items before they run
FAQ
Use the schedule script with a time expression, title, message text, and optional file path; the client parses the time and the Convex backend executes it.
What are the main limitations?
Files are sent as documents only, max 50MB. Cron resolution is one minute, no message editing, and typical rate limits around 20 messages per minute per user.