telegram-pimp

Active router for ALL Telegram requests — classifies by use case (bots, mini apps, payments, inline, channels, webhooks, login) and routes to the correct telegram skill. Use when anything involves Telegram bots, Mini Apps, Stars payments, inline queries, channel management, webhooks, or Telegram Login Widget.

Model	Source
sonnet	pack: telegram

Full Reference

If the request involves Telegram in ANY way — bots, mini apps, Stars, inline queries, channels, webhooks, login — you MUST route through this skill FIRST.

This is not optional. This is not negotiable. You cannot skip this.

Telegram Pimp

The orchestration layer for all Telegram development. Not documentation — an active router. Every Telegram request flows through this routing table before any response.

Mandatory Announcement — FIRST OUTPUT before anything else:

┏━ 📱 telegram-pimp ━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ [one-line description of what request/routing] ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

No exceptions. Box frame first, then route.

Quick Context

Telegram Bot API 9.5 (March 2026) — the current stable release. Three developer audiences: bot devs (REST Bot API), mini-app devs (WebApp SDK), and channel operators (admin rights).

Socratic Discovery Flow

Use when intent is vague — “I want to build a Telegram bot/thing”. Max 3 questions, then route.

Q1: "What's the core interaction?"
    → Menu/button responses        → telegram-bot-api
    → Inline search (@mention)     → telegram-inline
    → Payment / digital goods      → telegram-stars
    → Web app embedded in chat     → telegram-mini-apps
    → Push notifications/alerts    → telegram-webhooks

Q2: "Who triggers it?"
    → User messages the bot        → telegram-bot-api or telegram-webhooks
    → User finds via @mention      → telegram-inline
    → Admin push / channel post    → telegram-channels
    → External system webhook      → telegram-webhooks

Q3: "Is money involved?"
    → Yes, digital goods / tips    → telegram-stars
    → No                           → skip Stars, route by Q1/Q2

After 3 questions, route with confidence. Never ask a 4th.

Routing Table

Request Pattern	Skill
Send messages, keyboards, media, bot commands, getUpdates	`telegram-bot-api`
Bot API methods, types, rate limits, error codes	`telegram-bot-api`
Mini App, TWA, Telegram Web App, WebApp SDK, initData	`telegram-mini-apps`
CloudStorage, DeviceStorage, SecureStorage, TWA theming	`telegram-mini-apps`
Stars payment, XTR, sendInvoice, digital goods, refund	`telegram-stars`
Star subscriptions, pre-checkout, successful_payment	`telegram-stars`
Inline bot, answerInlineQuery, inline keyboard, callback query	`telegram-inline`
InlineQueryResult, switch_inline_query, cache_time	`telegram-inline`
Channel management, group admin, chatAdminRights, invite link	`telegram-channels`
Pinning messages, restricting members, negative permissions	`telegram-channels`
setWebhook, getUpdates polling, BotFather, bot setup	`telegram-webhooks`
secret_token validation, webhook security, bot lifecycle	`telegram-webhooks`
Telegram Login Widget, auth widget, hash validation	`telegram-login`
Login widget embed, user data, bot token verification	`telegram-login`

Hard Rules

Never respond about Telegram before invoking the target skill
No summarizing, planning to invoke, or explaining what you’re about to do
If two skills apply, invoke the PRIMARY one (closest to the core question)
If unclear after state detection, use Socratic flow (max 3 questions)
The skill’s reference docs have verified facts — always defer to them
TDLib/MTProto and TON blockchain are OUT OF SCOPE — don’t route there