← ClaudeAtlas

tg-capability-maplisted

Use before promising a Telegram feature or designing around one: what a bot can do in Bot API, what lives only in the client or MTProto (scheduled posts, channel stats, poll stats, channel stories, folders, boosts, welcome messages, communities), and what never to promise from a bot.
serejaris/telegram-skills · ★ 41 · AI & Automation · score 87
Install: claude install-skill serejaris/telegram-skills
# tg-capability-map A map with no code. Absence from Bot API was established from the [method list](https://core.telegram.org/bots/api) at Bot API 10.3 (August 24, 2026), checked on 2026-10-30. In the tables, **Since** is when the feature appeared where known, and **Checked** is the date the address was read. MTProto methods are named so you can find them; building an account client is a separate decision. ## How to use 1. Find the row. A bot can do only what the **Bot API** column shows. 2. A row with "no" in that column is off the table for a bot: name the alternative (a person in the client, or an account session) in your plan. 3. Open the address when the answer decides the work. ## Bot API only reads or partly reaches it | Capability | Bot API | Client or MTProto | Since | Checked | Source | |---|---|---|---|---|---| | Scheduled post | no; `SCHEDULE_BOT_NOT_ALLOWED`. Run your own timer | `schedule_date` on `messages.sendMessage`, `messages.sendMedia` | long-standing | 2026-10-30 | https://core.telegram.org/method/messages.sendMessage | | Repeating scheduled post | no | `schedule_repeat_period`, Premium, one message, seven fixed intervals from 1 day to 365 days | 2025-11-19 | 2026-10-30 | https://core.telegram.org/api/scheduled-messages | | Channel stats | no; `Message` has no view or forward counter | `stats.getBroadcastStats`, `stats.getMessageStats`; channels of a certain size | long-standing | 2026-10-30 | https://core.telegram.org/api/stats | | Poll stats | no |