domains / families / software-engineering / telegram

telegram

combined

OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs). Integracao completa com Telegram Bot API. Setup com BotFather, mensagens, webhooks, inline keyboards, grupos, canais. Boilerplates Node.js e Python.

When to use

• 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.
• When the user mentions "telegram" or related topics
• When the user mentions "bot telegram" or related topics
• When the user mentions "telegram bot" or related topics
• When the user mentions "api telegram" or related topics
• When the user mentions "chatbot telegram" or related topics
• When the user mentions "mensagem telegram" or related topics

When not to use

• The task is unrelated to telegram
• A simpler, more specific tool can handle the request
• The user needs general-purpose assistance without domain expertise
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

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.