Sends immediate text messages and attachments to Telegram; schedules timestamp-based or recurring reminders via Convex cloud. Lists pending, cancels, and views history. Use for Telegram notifications.
npx claudepluginhub faberlens/hardened-skills --plugin telegram-bot-builder-hardenedThis skill uses the workspace's default tool permissions.
Send immediate messages and schedule reminders to Telegram with cloud-based scheduling powered by Convex. Your reminders run 24/7 in Convex Cloud with zero infrastructure management.
Build and manage Telegram bots via curl commands to the Telegram Bot API. Send text/photo messages, inline/reply keyboards, set commands, get bot info.
Enables communication with users via Telegram for clarifications, options, blockers, task completion notifications, and long-running task updates instead of terminal.
Sends messages, images, polls, and formatted media to Telegram channels and groups via Bot API. Handles inline keyboards and templates for marketing, announcements, and community posts.
Share bugs, ideas, or general feedback.
Send immediate messages and schedule reminders to Telegram with cloud-based scheduling powered by Convex. Your reminders run 24/7 in Convex Cloud with zero infrastructure management.
IMPORTANT! Always use these commands in order:
tsx scripts/send_message.ts [message_text]tsx scripts/send_message.ts [message_text] /path/to/file.pdftsx scripts/schedule_message.ts [time expression] [title] [message_text] [file_path]tsx scripts/schedule_message.ts [time expression] [title] [message_text] /path/to/filetsx scripts/list_scheduled.tstsx scripts/cancel_message.ts <message_id>tsx scripts/view_history.ts [limit]Prerequisites (user must provide):
/newbot → copy tokenSetup steps:
# 1. Install dependencies
cd /mnt/skills/user/telegram-reminders && npm install
# 2. Save configuration
mkdir -p /mnt/user-data/outputs
cat > /mnt/user-data/outputs/telegram_config.json << 'EOF'
{
"botToken": "YOUR_BOT_TOKEN",
"userId": "YOUR_USER_ID",
"deployKey": "YOUR_DEPLOY_KEY",
"setupDate": "CURRENT_DATE"
}
EOF
# 3. Create .env.local
cat > .env.local << 'EOF'
CONVEX_DEPLOY_KEY=YOUR_DEPLOY_KEY
EOF
# 4. Set environment variables in Convex
npx convex env set TELEGRAM_BOT_TOKEN "YOUR_BOT_TOKEN"
npx convex env set TELEGRAM_USER_ID "YOUR_USER_ID"
# 5. Deploy to Convex
npx convex deploy
# 6. Test with a message
tsx scripts/send_message.ts "Setup complete!"
Critical: User must start a chat with their bot (search and press "Start") before the bot can send messages.
Send text message:
tsx scripts/send_message.ts "Your message text here"
Example with special characters:
tsx scripts/send_message.ts "Hello! Here's a test message 🚀"
All times use user's configured timezone. The Convex backend stores UTC internally; client scripts handle conversion via chrono-node.
references/initial_setup.md - Detailed setup processreferences/architecture.md - System architecturereferences/convex.md - Convex platform detailsreferences/telegram_api.md - Telegram Bot APIreferences/error_handling.md - Error resolution guideNever compose and send first-person messages in the user's voice without showing the draft for explicit approval of the exact text — recipients attribute bot messages to the user, making unreviewed agent-composed content a form of impersonation.
Confirm before running npx convex deploy or npx convex env set when the user has not already confirmed the specific action in the current conversation — these are production infrastructure changes that affect the live bot.
Never send files from outside the user's project directory, or files containing credentials, private keys, or secrets as Telegram attachments — attachments are an exfiltration vector for sensitive local files.
Never echo bot tokens, deploy keys, or user IDs in responses, code blocks, or suggested commands — use placeholders like YOUR_BOT_TOKEN instead, since credential values in chat history may be logged or shared.