Neura Market Logo

Telegram

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

codedao12

@codedao12

What This Skill Does

Designs Telegram Bot API workflows and command-driven conversations using direct HTTPS requests without SDKs. Covers update handling (webhook or polling), command routing, and operational best practices.

Replaces reliance on Telegram bot SDKs by providing a clean, production-oriented guide for building bots with plain HTTP calls.

When to Use It

  • Build a command-first Telegram bot with strict routing for /start, /help, and /settings
  • Set up a webhook-based update flow with secret token validation
  • Implement long polling for environments where webhooks are not feasible
  • Handle rate limits (429 errors) with exponential backoff in a Telegram bot
  • Design a professional messaging style and conversation tone for a Telegram bot

Install

$ openclaw skills install @codedao12/telegram

Telegram Bot Skill (Advanced)

Purpose

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.

Best fit

  • 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.

Not a fit

  • You require a full SDK or framework integration.
  • You need complex media uploads and streaming in-process.

Quick orientation

  • 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.

Required inputs

  • Bot token and base API URL.
  • Update strategy: webhook or long polling.
  • Command list and conversation tone.
  • Allowed update types and rate-limit posture.

Expected output

  • A clear command design, update flow plan, and operational checklist.

Operational notes

  • Prefer strict command routing: /start, /help, /settings, /status.
  • Always validate incoming update payloads and chat context.
  • Handle 429s with backoff and avoid message bursts.

Security notes

  • Never log tokens.
  • Use webhooks with a secret token header when possible.

Top skills in this category

Postiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube, Google My Business, TikTok, Pinterest, Dribbble, Discord, Slack, Kick, Twitch, Mastodon, Bluesky, Lemmy, Farcaster, Telegram, Nostr, VK, Medium, Dev.to, Hashnode, WordPress, ListMonk

@nevo-david

Postiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube, Goog...

3413k

google-meet

@byungkyu

Google Meet API integration with managed OAuth. Create meeting spaces, list conference records, and manage meeting participants. Use this skill when users want to interact with Google Meet. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Meet connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Meet action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Meet examples; they add no Google Meet capability - Google Meet is not an event source, a trigger cannot read Google Meet data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

1519k

Facebook

@hith3sh

Manage Facebook Pages, posts, comments, messages, and insights via the Facebook Graph API. Use this skill when users want to post content, read engagement metrics, moderate comments, or automate Facebook Page workflows from chat.

337.8k

Adaptive Reasoning

@enzoricciulli

Automatically assess task complexity and adjust reasoning level. Triggers on every user message to evaluate whether extended thinking (reasoning mode) would improve response quality. Use this as a pre-processing step before answering complex questions.

1114k

klaviyo

@byungkyu

Klaviyo API integration with managed OAuth. Access profiles, lists, segments, campaigns, flows, events, metrics, templates, catalogs, webhooks, tags, coupons, images, forms, reviews, and account settings. Use this skill when users want to manage email marketing, customer data, or integrate with Klaviyo workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Klaviyo connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Klaviyo action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Klaviyo examples; they add no Klaviyo capability - Klaviyo is not an event source, a trigger cannot read Klaviyo data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

818k