# Send Telegram Bot API to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text 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. ``` ### Upgrade existing ```text 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. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "telegram-bot-api", "name": "Telegram Bot API", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/ivangdavila/telegram-bot-api", "canonicalUrl": "https://clawhub.ai/ivangdavila/telegram-bot-api", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/telegram-bot-api", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=telegram-bot-api", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "errors.md", "formatting.md", "keyboards.md", "media.md", "memory-template.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "telegram-bot-api", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-09T19:36:34.649Z", "expiresAt": "2026-05-16T19:36:34.649Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=telegram-bot-api", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=telegram-bot-api", "contentDisposition": "attachment; filename=\"telegram-bot-api-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "telegram-bot-api" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/telegram-bot-api" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/telegram-bot-api", "downloadUrl": "https://openagent3.xyz/downloads/telegram-bot-api", "agentUrl": "https://openagent3.xyz/skills/telegram-bot-api/agent", "manifestUrl": "https://openagent3.xyz/skills/telegram-bot-api/agent.json", "briefUrl": "https://openagent3.xyz/skills/telegram-bot-api/agent.md" } } ``` ## Documentation ### Setup On first use, read setup.md for integration guidelines. ### When to Use User needs to interact with the Telegram Bot API. Building bots, sending messages, handling updates, setting up webhooks, creating keyboards, or managing bot commands. ### Architecture 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 ### Quick Reference TopicFileSetup processsetup.mdMemory templatememory-template.mdAll API methodsmethods.mdMessage formattingformatting.mdKeyboards & buttonskeyboards.mdWebhooks & pollingwebhooks.mdMedia handlingmedia.mdError codeserrors.md ### 1. API Base URL All requests go to: https://api.telegram.org/bot{TOKEN}/{METHOD} Never expose the token in logs or user-visible output. ### 2. Required Parameters by Method 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—— ### 3. Parse Mode Selection FormatUse whenEscape charsMarkdownV2Rich formatting needed_*[]()~\\>#+-=HTMLComplex nesting, safer<>&NonePlain text onlyNone Default to HTML — fewer escape issues than MarkdownV2. ### 4. Chat ID Types TypeFormatExampleUserPositive integer123456789GroupNegative integer-123456789Supergroup/Channel-100 prefix-1001234567890 ### 5. Rate Limits 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. ### 6. Message Length Limits TypeLimitText message4096 charsCaption1024 charsCallback data64 bytesInline query256 chars Split long messages at sentence boundaries, not mid-word. ### 7. Keyboard Best Practices 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 ### Common Traps 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. ### External Endpoints 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. ### Security & Privacy 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 ### Trust By using this skill, data is sent to Telegram's Bot API servers. Only install if you trust Telegram with your bot's messages. ### Related Skills Install with clawhub install if user confirms: api — REST API best practices http — HTTP protocol essentials json — JSON parsing and manipulation ### Feedback If useful: clawhub star telegram-bot-api Stay updated: clawhub sync ## Trust - Source: tencent - Verification: Indexed source record - Publisher: ivangdavila - Version: 1.0.0 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-05-09T19:36:34.649Z - Expires at: 2026-05-16T19:36:34.649Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/telegram-bot-api) - [Send to Agent page](https://openagent3.xyz/skills/telegram-bot-api/agent) - [JSON manifest](https://openagent3.xyz/skills/telegram-bot-api/agent.json) - [Markdown brief](https://openagent3.xyz/skills/telegram-bot-api/agent.md) - [Download page](https://openagent3.xyz/downloads/telegram-bot-api)