Agent skill · software engineering · anthropics
configure
Set up the Telegram channel — save the bot token and review access policy. Use when the user pastes a Telegram bot token, asks to configure Telegram, asks "how do I set this up" or "who can reach me," or wants to check channel status.
Why this skill is useful
Adds specific commands and procedures for configuring Telegram bot access that the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 33,212 stars on the source repository.
What this skill does
/telegram:configure — Telegram Channel Setup Writes the bot token to <state-dir>/.env and orients the user on access policy. The server reads both files at boot. Resolve the state directory first (it may be overridden for multi-bot or per-project setups): Use the printed path everywhere below in place of <state-dir>. The default is ~/.claude/channels/telegram. Arguments passed: $ARGUMENTS --- Dispatch on arguments No args — status and guidance Read both state files and give the user a complete picture: 1. Token — check <state-dir>/.env for TELEGRAMBOTTOKEN. Show set/not-set; if set, show first 10 chars masked (123456789:...). 2. Access — read <state-dir>/access.json (missing file = defaults: dmPolicy: "pairing", empty allowlist). Show: DM policy and what it means in one line Allowed senders: count, and list display names or IDs Pending pairings: count, with codes and display names if any 3. What next — end with a concrete next step based on state: No token → "Run /telegram:configure <token> with the token from BotFather." Token set, policy is pairing, nobody allowed → "DM your bot on Telegram. It replies with a code; approve with /telegram:access pair <code>." Token set, someone allowed → "Ready. DM your bot to reach the assistant." Push toward lockdown — always. The goal for every setup is allowlist with a defined list. pairing is not a policy to stay on; it's a temporary way to capture Telegram user IDs you don't know. Once the IDs are in, pairing has done its job and should be turned off. Drive the conversation this way: 1. Read the allowlist. Tell the user who's in it. 2. Ask: "Is that everyone who should reach you through this bot?" 3. If yes and policy is still pairing → "Good. Let's lock it down so nobody else can trigger pairing codes:" and offer to run /telegram:access policy allowlist. Do this proactively — don't wait to be asked. 4. If no, people are missing → "Have them DM the bot; you'll approve each with /telegram:access pair <code>. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/configure--53d525