Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build Telegram bots with correct API calls, message formatting, keyboards, and webhook setup.
Build Telegram bots with correct API calls, message formatting, keyboards, and webhook setup.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
On first use, read setup.md for integration guidelines.
User needs to interact with the Telegram Bot API. Building bots, sending messages, handling updates, setting up webhooks, creating keyboards, or managing bot commands.
Memory lives in ~/telegram-bot-api/. See memory-template.md for structure. ~/telegram-bot-api/ ├── memory.md # Bot tokens, preferences, defaults ├── bots/ # Per-bot configurations │ └── {botname}.md # Token, webhook URL, defaults └── templates/ # Reusable message templates
TopicFileSetup processsetup.mdMemory templatememory-template.mdAll API methodsmethods.mdMessage formattingformatting.mdKeyboards & buttonskeyboards.mdWebhooks & pollingwebhooks.mdMedia handlingmedia.mdError codeserrors.md
All requests go to: https://api.telegram.org/bot{TOKEN}/{METHOD} Never expose the token in logs or user-visible output.
MethodRequiredOptional (common)sendMessagechat_id, textparse_mode, reply_markup, disable_notificationsendPhotochat_id, photocaption, parse_modesendDocumentchat_id, documentcaption, thumbnailgetUpdates—offset, limit, timeoutsetWebhookurlcertificate, max_connectionsdeleteWebhook—drop_pending_updatesgetMe——
FormatUse whenEscape charsMarkdownV2Rich formatting needed_*[]()~\>#+-=HTMLComplex nesting, safer<>&NonePlain text onlyNone Default to HTML — fewer escape issues than MarkdownV2.
TypeFormatExampleUserPositive integer123456789GroupNegative integer-123456789Supergroup/Channel-100 prefix-1001234567890
ScopeLimitSame chat1 msg/secDifferent chats30 msg/secGroups20 msg/min per groupBulk notificationsUse sendMessage with different chat_ids When hitting 429 errors, use exponential backoff starting at retry_after seconds.
TypeLimitText message4096 charsCaption1024 charsCallback data64 bytesInline query256 chars Split long messages at sentence boundaries, not mid-word.
Inline keyboards (in message): Max 8 buttons per row Max 100 buttons total Use callback_data for bot actions Use url for external links Reply keyboards (below input): Use for frequent options one_time_keyboard: true to hide after use resize_keyboard: true for better mobile UX
Forgetting to escape MarkdownV2 → Message fails silently or partially. Use HTML instead, or escape all special chars. Using wrong chat_id format → Groups need negative IDs. Supergroups/channels need -100 prefix. Not handling 429 errors → Bot gets temporarily blocked. Always implement retry logic. Exposing bot token → Anyone can control your bot. Never log or display tokens. Sending too fast to groups → 20 msg/min limit. Queue messages with delays. Large file uploads → 50MB limit for sendDocument. Use URL method for larger files. Webhook not HTTPS → Telegram requires valid SSL certificate.
EndpointData SentPurposehttps://api.telegram.org/bot{TOKEN}/*Messages, media, commandsAll bot operations No other data is sent externally. Bot token is required for all requests.
Data that leaves your machine: Messages and media sent via the Bot API Bot token in every request (required by Telegram) Data that stays local: Bot configurations in ~/telegram-bot-api/ Message templates This skill does NOT: Store message content long-term Access user data beyond what Telegram provides Make requests to endpoints other than api.telegram.org
By using this skill, data is sent to Telegram's Bot API servers. Only install if you trust Telegram with your bot's messages.
Install with clawhub install <slug> if user confirms: api — REST API best practices http — HTTP protocol essentials json — JSON parsing and manipulation
If useful: clawhub star telegram-bot-api Stay updated: clawhub sync
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.