Telegram
OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs).
codedao12
@codedao12
What This Skill Does
Designs Telegram Bot API workflows and command-driven conversations using direct HTTPS requests without SDKs. Covers update handling (webhook or polling), command routing, and operational best practices.
Replaces reliance on Telegram bot SDKs by providing a clean, production-oriented guide for building bots with plain HTTP calls.
When to Use It
- Build a command-first Telegram bot with strict routing for /start, /help, and /settings
- Set up a webhook-based update flow with secret token validation
- Implement long polling for environments where webhooks are not feasible
- Handle rate limits (429 errors) with exponential backoff in a Telegram bot
- Design a professional messaging style and conversation tone for a Telegram bot
Install
$ openclaw skills install @codedao12/telegramTelegram Bot Skill (Advanced)
Purpose
Provide a clean, production-oriented guide for building Telegram bot workflows via the Bot API, focusing on command UX, update handling, and safe operations using plain HTTPS.
Best fit
- You want a command-first bot that behaves professionally.
- You need a reliable update flow (webhook or polling).
- You prefer direct HTTP calls instead of libraries.
Not a fit
- You require a full SDK or framework integration.
- You need complex media uploads and streaming in-process.
Quick orientation
- Read
references/telegram-bot-api.mdfor endpoints, update types, and request patterns. - Read
references/telegram-commands-playbook.mdfor command UX and messaging style. - Read
references/telegram-update-routing.mdfor update normalization and routing rules. - Read
references/telegram-request-templates.mdfor HTTP payload templates. - Keep this SKILL.md short and use references for details.
Required inputs
- Bot token and base API URL.
- Update strategy: webhook or long polling.
- Command list and conversation tone.
- Allowed update types and rate-limit posture.
Expected output
- A clear command design, update flow plan, and operational checklist.
Operational notes
- Prefer strict command routing:
/start,/help,/settings,/status. - Always validate incoming update payloads and chat context.
- Handle 429s with backoff and avoid message bursts.
Security notes
- Never log tokens.
- Use webhooks with a secret token header when possible.
Top skills in this category
Postiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube, Google My Business, TikTok, Pinterest, Dribbble, Discord, Slack, Kick, Twitch, Mastodon, Bluesky, Lemmy, Farcaster, Telegram, Nostr, VK, Medium, Dev.to, Hashnode, WordPress, ListMonk
@nevo-davidPostiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube, Goog...
Adaptive Reasoning
@enzoricciulliAutomatically assess task complexity and adjust reasoning level. Triggers on every user message to evaluate whether extended thinking (reasoning mode) would improve response quality. Use this as a pre-processing step before answering complex questions.
Moltbot Best Practices
@nextfrontierbuildsBest practices for AI agents - Cursor, Claude, ChatGPT, Copilot. Avoid common mistakes. Confirms before executing, drafts before publishing. Vibe-coding essential.
Reminder
@reed1898Capture natural-language events, save to your workspace, and schedule Telegram reminders with automatic cron notifications and upcoming event queries.
Openclaw Skill
@peturgeorgievvSchedule and manage social media posts across TikTok, Instagram, Facebook, X (Twitter), YouTube, LinkedIn, Threads, Bluesky, Pinterest, Telegram, and Google...