Configure

anthropics/claude-plugins-official/external_plugins/telegram/skills/configure

作者 anthropics315c4e48967d9541c29c3c656441dded353ca7aa无许可证47K 个星标收录于 2026年11月20日更新于 2026年11月20日仓库今天更新

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.

精选包含脚本效率与工作流
AI 生成的概览

配置 Telegram 频道:保存机器人令牌、查看状态并引导收紧访问策略。

功能
先解析频道状态目录,再把 Telegram 机器人令牌写入 .env 文件并设置受限权限,也可清除令牌。无参数运行时读取令牌与访问配置文件,报告令牌是否已设置、私信策略、允许的发送者与待处理的配对,并给出下一步建议。它还会引导用户切换到 allowlist 策略,并说明令牌变更需重启会话。
适用场景
适用于用户粘贴 Telegram 机器人令牌、询问如何配置 Telegram 或谁能联系到自己,或想查看频道配置状态时。
运行要求
需要对频道状态目录的读取、写入与 shell 权限(ls、mkdir、echo、chmod),以及来自 BotFather 的 Telegram 机器人令牌。无需网络访问或额外软件包;该技能不附带独立脚本。

/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):

bash
echo "${TELEGRAM_STATE_DIR:-${CLAUDE_CONFIG_DIR:-$HOME/.claude}/channels/telegram}"

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 TELEGRAM_BOT_TOKEN. 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>. Run this skill again once everyone's in and we'll lock it."
  5. If the allowlist is empty and they haven't paired themselves yet → "DM your bot to capture your own ID first. Then we'll add anyone else and lock it down."
  6. If policy is already allowlist → confirm this is the locked state. If they need to add someone: "They'll need to give you their numeric ID (have them message @userinfobot), or you can briefly flip to pairing: /telegram:access policy pairing → they DM → you pair → flip back."

Never frame pairing as the correct long-term choice. Don't skip the lockdown offer.

<token> — save it

  1. Treat $ARGUMENTS as the token (trim whitespace). BotFather tokens look like 123456789:AAH... — numeric prefix, colon, long string.
  2. mkdir -p the resolved <state-dir>.
  3. Read existing .env if present; update/add the TELEGRAM_BOT_TOKEN= line, preserve other keys. Write back, no quotes around the value.
  4. chmod 600 on <state-dir>/.env — the token is a credential.
  5. Confirm, then show the no-args status so the user sees where they stand.

clear — remove the token

Delete the TELEGRAM_BOT_TOKEN= line (or the file if that's the only line).


Implementation notes

  • The channels dir might not exist if the server hasn't run yet. Missing file = not configured, not an error.
  • The server reads .env once at boot. Token changes need a session restart or /reload-plugins. Say so after saving.
  • access.json is re-read on every inbound message — policy changes via /telegram:access take effect immediately, no restart.

来源与署名

来源:anthropics/claude-plugins-official位于external_plugins/telegram/skills/configure提交315c4e4

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

在 README 中添加徽章

向读者展示该技能已收录于 SourceWeft,徽章链接到本页。

“Listed on SourceWeft”徽章预览
[![Listed on SourceWeft](https://sourceweft.com/badge/skills/gh-anthropics-claude-plugins-official-configure-external-plugins-telegram-skills-configure-21db87490a713169.svg)](https://sourceweft.com/skills/gh-anthropics-claude-plugins-official-configure-external-plugins-telegram-skills-configure-21db87490a713169?utm_source=readme&utm_medium=badge)

举报或申请下架