domains / software-engineering / telegram-bot-api / telegram

telegram

Skill card

combined

The two skills overlap in scope (Telegram Bot API integration) but disagree on implementation strategy and provide different, non-redundant operational constraints. The first copy (sickn33) is a high-level wrapper that defers to a 'detailed guide' and emphasizes boilerplates for Node.js/Python, while the second copy (LeoYeAI) explicitly forbids SDKs in favor of direct HTTPS requests and provides specific operational rules for command routing, rate limiting, and security. Crowning one would hide the other's specific architectural constraints (SDK vs. raw HTTP) and operational checklists.

Repositories

Other copies

Combined skill

---
name: telegram
description: Professional Telegram Bot API integration guide covering setup, messaging, webhooks, and command-driven workflows.
---

# Telegram Bot API Skill

## When to Use
- When the user requests a Telegram bot, chatbot, or API integration.
- When designing command-driven conversations or update handling flows.

## Prerequisites
- Bot token from BotFather.
- Decision on update strategy: Webhook or Long Polling.
- Decision on implementation style: SDK/Library (Node.js/Python) or Direct HTTPS.

## Implementation Strategy
1. **Choose Approach**:
   - **SDK Approach**: Use Node.js or Python boilerplates for rapid development with high-level abstractions.
   - **Direct HTTPS Approach**: Use plain HTTP requests for lightweight, dependency-free implementations. Avoid SDKs if strict control over payloads is required.

2. **Command Design**:
   - Implement strict command routing for core commands: `/start`, `/help`, `/settings`, `/status`.
   - Define conversation tone and command list clearly.

3. **Update Handling**:
   - **Webhooks**: Use a secret token header for security. Validate incoming update payloads and chat context.
   - **Polling**: Implement robust error handling for network interruptions.

4. **Rate Limiting & Reliability**:
   - Handle HTTP 429 responses with exponential backoff.
   - Avoid message bursts to prevent triggering rate limits.

## Security Requirements
- **Never** log bot tokens or sensitive user data.
- Always validate incoming update payloads to prevent injection or malformed data errors.
- Use webhook secret tokens when possible.

## Validation
- Test command routing for all defined commands.
- Verify update flow (webhook or polling) handles edge cases (e.g., missing chat ID, invalid token).
- Confirm rate-limit handling works under load.