telegram-bot-stinger

Implements Telegram bots with grammY, aiogram, webhooks, Mini Apps, and Stars payments.

84|37|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill telegram-bot-stinger-legioncodeinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: telegram-bot-stinger
Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/main/src/skills/telegram-bot-stinger
Command: npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill telegram-bot-stinger-legioncodeinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building Telegram bots in 2026 requires navigating four major Bot API releases, a mandatory shift to Telegram Stars for digital goods, dual initData validation paths, and framework churn (Telegraf abandoned, grammY still v1). This Skill encodes the current, research-backed playbook so you don't ship outdated patterns or insecure Mini App authentication. ## Core Features & Use Cases - Framework Selection: Decision tree for grammY v1.x (TypeScript) vs aiogram 3.x (Python), with verified version facts and migration guidance away from abandoned Telegraf. - Webhook & Deployment Setup: HTTPS requirements, allowed ports, secret_token validation, the 409 Conflict polling/webhook mutual exclusion fix, and quantitative webhook-vs-polling thresholds. - Mini Apps Security: Complete HMAC-SHA256 and Ed25519 initData validation algorithms with auth_date expiry checks, plus WebApp JS SDK coverage (MainButton, haptics, CloudStorage). - Telegram Stars Payments: Mandatory XTR flow for digital goods, sendInvoice parameters, the 10-second pre_checkout_query window, and successful_payment fulfillment handlers. - Use Case: You need to launch a paid Telegram Mini App. The Skill walks you through grammY scaffolding, webhook deployment behind nginx, server-side initData validation, and a Stars checkout flow with a pre-launch checklist. ## Quick Start Use the telegram-bot-stinger skill to scaffold a production grammY bot with webhook deployment, validated Mini App initData, and a Stars payment flow.

Frequently Asked Questions about telegram-bot-stinger

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

FAQPage Schema
How do I set up a Telegram bot webhook in production?▼

Deploy an HTTPS endpoint on port 443, 80, 88, or 8443, then call setWebhook with your URL, a secret_token, and scoped allowed_updates. Validate the X-Telegram-Bot-Api-Secret-Token header on every request and verify with getWebhookInfo.

grammY vs aiogram: which Telegram bot framework should I use?▼

Use grammY v1.x for TypeScript/JavaScript projects and aiogram 3.x for Python. Both track Bot API releases within days. Telegraf is abandoned and python-telegram-bot is only recommended for legacy codebases.

How do I validate Telegram Mini App initData server-side?▼

Parse the initData query string, remove the hash field, sort remaining key=value pairs alphabetically, join with newlines, then compute HMAC-SHA256 using a key derived from HMAC-SHA256 of 'WebAppData' with your bot token. Also reject auth_date values older than one hour.

Why does my Telegram bot return 409 Conflict on getUpdates?▼

A 409 Conflict means a webhook is active while you call getUpdates; webhook and long-polling are mutually exclusive. Call deleteWebhook before switching to polling mode.

Can I charge fiat currency for digital goods in a Telegram bot?▼

No. Telegram Stars (currency code XTR) are mandatory for all digital goods due to Apple and Google app store compliance. Use an empty provider_token for Stars; fiat via a payment provider is only allowed for physical goods.

When should I use MTProto instead of the Telegram Bot API?▼

Escalate to MTProto via Telethon or TDLib only when the Bot API cannot do the task, such as reading channels the bot is not in, automating user accounts, or accessing full message history. Check Bot API 10.0 features like guest mode first.