← ClaudeAtlas

telegram-botlisted

Build, host and automate Telegram bots in TypeScript (grammY) or Python (aiogram, python-telegram-bot) — BotFather setup, webhooks vs long polling, commands, deep links, keyboards, groups and channels, broadcasts and rate limits, AI bots that stream replies, Business bots, managed bots, guest mode, ephemeral messages and launching a Mini App. Use this skill whenever the user creates or edits a Telegram bot, asks about BotFather, a bot token, webhooks, getUpdates, bot commands, start parameters, mass messaging, posting to a channel on a schedule, a support or AI chat bot, or hosting a bot on Vercel, a VPS or another serverless platform. Safety rule even without loading this skill. Never open, cat or print .env to debug a token (check variable names only with grep -o '^[A-Za-z_]*=' .env) and never write a real token into source files.
daniilganiev/telegram-dev · ★ 0 · AI & Automation · score 72
Install: claude install-skill daniilganiev/telegram-dev
# Telegram bot The Bot API changes every month or two (10.4 in November 2026). Before using any method or field you are not sure about, check https://core.telegram.org/bots/api-changelog. Frameworks lag behind the API; when a framework has no wrapper yet, call the method through the framework's raw API (`bot.api.raw.<method>` in grammY, a custom `TelegramMethod` in aiogram) instead of inventing a wrapper that doesn't exist. ## Stack | Language | Default | Notes | |---|---|---| | TypeScript | grammY | Node, Deno, Bun, edge; webhook adapters for most hosts | | Python | aiogram 3 | async, routers, FSM; `python-telegram-bot` if the project already uses it | Use what the project already has. Look up current setup in the framework docs rather than writing boilerplate from memory. ## Setup 1. `@BotFather` → `/newbot`. The token goes into a backend env var (`BOT_TOKEN`), never into the repo, the Mini App bundle or a chat message. A leaked token is revoked in @BotFather. Claude never writes a real token into source, passes it inline in a command or reads `.env` to see it; code reads `process.env.BOT_TOKEN` / `os.environ["BOT_TOKEN"]`. **Debugging 401 / token errors without seeing the token:** list variable names only (`grep -o '^[A-Za-z_]*=' .env`), compare them with what the code reads, check that something loads `.env` (`dotenv`, `--env-file`, the host's env settings). If the value itself may be wrong, ask the user to call `getMe` with it in their own term