telegram

Design Telegram Bot API workflows with HTTPS, webhook, and long-polling.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nakamotosai/chii --skill telegram-nakamotosai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: telegram
Source: https://github.com/nakamotosai/chii/tree/main/skills/telegram
Command: npx skills add https://github.com/nakamotosai/chii --skill telegram-nakamotosai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs).

Core Features & Use Cases

  • Command UX focusing on clean interactions and predictable update handling.
  • Supports webhook or long-polling update flow with direct HTTP requests (no SDKs).
  • Safe operations with token management and rate-limiting considerations.

Quick Start

Configure your bot token and API URL, choose webhook or long polling, and implement the /start, /help, /settings, and /status commands.

Frequently Asked Questions about telegram

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Telegram bot using plain HTTP requests without an SDK?

To build a Telegram bot using plain HTTP requests, configure your bot token and API URL, choose webhook or long-polling for update routing, and implement commands like /start and /help via direct HTTPS calls.

What is the difference between webhook and long-polling for Telegram Bot API updates?

Webhook and long-polling differ in update delivery: webhooks receive pushed updates at your HTTPS endpoint, while long-polling actively fetches updates. Both handle Telegram Bot API routing via direct HTTP requests.

How do I handle rate limits and secure token management for Telegram bots?

Handle Telegram bot rate limits by enforcing backoff on 429 responses. Secure token management is maintained by configuring bot tokens safely during direct HTTPS request operations.

Can I design command-driven conversations for Telegram bots using direct HTTPS?

Yes, you can design command-driven conversations for Telegram bots using direct HTTPS. The workflow covers command UX, predictable update handling, and input validation for interactions like /settings and /status.

Do I need a Telegram bot SDK to implement command UX and update routing?

No, you do not need a Telegram bot SDK. You can implement command UX, update routing, and efficient request handling using plain HTTPS requests with webhook or long-polling setups.

What are the limitations of using plain HTTP requests for Telegram Bot API workflows?

Limitations of using plain HTTP requests for Telegram Bot API workflows include manually enforcing input validation, idempotent handlers, and backoff on 429 rate limits without SDK abstractions.