telegram-bot-clilisted

# Telegram Bot API Why this is a skill and not an MCP: The community telegram MCPs (e.g. `@overpod/mcp-telegram`) ran in **MTProto user-bot mode** — i.e., logged in as YOUR account. That gave the agent read/write access to **all** your personal chats, contacts, files. Too much surface for a single-maintainer community package. The **Bot API**, by contrast: - Bot only sees chats it has been **explicitly added to** or that the user has **started** with `/start`. - Bot can read/post in those chats, send files, call inline keyboards. - Bot **cannot** read your DMs with other people, your channels you only consume, your secret chats, or your private messages. This is the right scope for an agent. ## Setup (one-time) ### 1. Create the bot 1. Telegram → message `@BotFather` → `/newbot` 2. Name it (e.g. "Walter Notifier") and pick a username (must end in `bot`, e.g. `walter_notifier_bot`). 3. BotFather returns a token like `8123456789:AAH...`. Save it as `WALTER_TELEGRAM_BOT_TOKEN` in your secrets store (Infisical workspace `walter-os`). ### 2. Get your chat ID ```bash # Start a chat with your bot in the Telegram app, send any message. # Then: curl -s "https://api.telegram.org/bot${WALTER_TELEGRAM_BOT_TOKEN}/getUpdates" | jq '.result[].message.chat' ``` Save the `id` field as `WALTER_TELEGRAM_CHAT_ID` in your secrets. ### 3. (Optional) Group / channel To use the bot in a group: add bot to group → BotFather command `/setprivacy` → `Disable` (so the bot can re