Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs).
OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs).
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.
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.
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.
You require a full SDK or framework integration. You need complex media uploads and streaming in-process.
Read references/telegram-bot-api.md for endpoints, update types, and request patterns. Read references/telegram-commands-playbook.md for command UX and messaging style. Read references/telegram-update-routing.md for update normalization and routing rules. Read references/telegram-request-templates.md for HTTP payload templates. Keep this SKILL.md short and use references for details.
Bot token and base API URL. Update strategy: webhook or long polling. Command list and conversation tone. Allowed update types and rate-limit posture.
A clear command design, update flow plan, and operational checklist.
Prefer strict command routing: /start, /help, /settings, /status. Always validate incoming update payloads and chat context. Handle 429s with backoff and avoid message bursts.
Never log tokens. Use webhooks with a secret token header when possible.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.