Telegram Bot API integration with managed authentication. Send messages, manage chats, handle updates, and interact with users through your Telegram bot. Use this skill when users want to send messages, create polls, manage bot commands, or interact with Telegram chats. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every `/telegram/` path goes to the Telegram Bot API and nowhere else; the methods documented here are the ones this skill uses, and the passthrough can also call other Bot API methods the bot token allows. Default to read calls, and confirm every send, edit, delete, or new connection with the user.
Stop documenting a download URL that requires the bot token. Telegram serves file bytes from api.telegram.org/file/bot<token>/<file_path>, and the old one-line note told the reader to use that path - which means obtaining the bot token and putting a live credential into a URL that lands in shell history, ps output, and proxy logs, contradicting this skill's own rule that the token never surfaces. The Files section now says not to construct it and to ask the user how a download should be authorized.