---
title: "Telegram access: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/anthropic-telegram-access/
description: "Pins the Telegram access skill, which resolves a state directory, refuses channel-originated edits, and will not approve a pairing without its code."
---

# Telegram access: review, setup & limitations · Undominated.ai

> Pins the Telegram access skill, which resolves a state directory, refuses channel-originated edits, and will not approve a pairing without its code.

[← Explore all skills](/skills/)

TELEGRAM ACCESS CONTROL / Anthropic

# Telegram access

Pins the Telegram access skill, which resolves a state directory, refuses channel-originated edits, and will not approve a pairing without its code.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/anthropics/claude-plugins-official/tree/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/skills/access)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 6 linked sources
 Publisher Anthropic
 Licence [Apache-2.0 ↗](https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/LICENSE)
 Revision 41f32e407b45
 [Read what was—and wasn’t—checked ↓](#review)

“Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Telegram channel.”

 [Anthropic · upstream description ↗](https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/skills/access/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The skill refuses access changes that arrive as a Telegram or Discord message and says those mutations must not be downstream of untrusted input.
- It resolves the state directory before editing access.json, stops on a missing or expired code, and will not auto-pick the only pending entry.

### A good fit for

 - Approving a Telegram pairing code from the terminal after the state directory has been resolved

### Weigh up before choosing

 - This review did not execute the resource.
- `/plugin install telegram@claude-plugins-official` installs the telegram plugin, including both skills and the channel server. It does not install this file alone.
- The plugin README says a shell TELEGRAM_BOT_TOKEN takes precedence over the env file. This access skill does not write that token.
- Sender ids are opaque strings and the skill says not to validate their format.
- ACCESS.md and server.ts were not opened. No channel server was started.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - external_plugins/telegram/skills/access/SKILL.md
- external_plugins/telegram/README.md
- external_plugins/telegram/LICENSE
- README.md
- LICENSE

### Our findings

 - Access changes from a channel notification are refused, and the user is told to run /telegram:access in the terminal.
- The state directory comes from TELEGRAM_STATE_DIR, then CLAUDE_CONFIG_DIR, then ~/.claude/channels/telegram, and that path is used for access.json.
- A missing or expired pairing code stops the approval, and the only pending code is not chosen automatically.
- The skill reads the access file before writing it and says it does not talk to Telegram.
- The missing-file default is pairing. Sender ids are not format-checked. Policy must be pairing, allowlist, or disabled.

### Not established by this review

 - The resource was not executed and its tools were not called.
- The state directory was not resolved and no access.json file was written.
- ACCESS.md, server.ts, and .mcp.json were not opened.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/README.md)

DOCUMENTED COMMAND

 /plugin install telegram@claude-plugins-official Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - The Telegram plugin README contains the line `/plugin install telegram@claude-plugins-official`. That installs the telegram plugin, not this file alone.
- The skill first prints the resolved state directory from TELEGRAM_STATE_DIR, CLAUDE_CONFIG_DIR, or the default under the home directory. This review did not print it.
- Allowlist edits are the `/telegram:access` commands. This review did not run them.

### Before you start

 - Claude Code
- The telegram plugin, because the install line adds that plugin rather than this file

### Compatibility

Claude Code

### Local Telegram allowlist edits under a resolved state directory

 - Read and write access.json under the resolved Telegram state directory
- Refuse those edits when the request arrives as a channel notification
- Do not talk to Telegram from this skill, and do not validate sender-id format

### Cost model

Apache-2.0; the skill was not run and no access file was written

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Telegram access SKILL.md ↗](https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/skills/access/SKILL.md) Checked 2026-10-14 https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/skills/access/SKILL.md Supports: channel refusal, state-directory resolution, and pairing-code stop
- [Telegram plugin README ↗](https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/README.md) Checked 2026-10-14 https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/README.md Supports: plugin install line and the channel relaunch requirement
- [Telegram plugin LICENSE ↗](https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/LICENSE) Checked 2026-10-14 https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/LICENSE Supports: Apache License, Version 2.0
- [Repository LICENSE ↗](https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/LICENSE) Checked 2026-10-14 https://github.com/anthropics/claude-plugins-official/blob/41f32e407b450055044f167db7ded5e8ff67d203/LICENSE Supports: Apache License, Version 2.0
- [2026-10-15 W08 source re-review at the existing pin ↗](https://raw.githubusercontent.com/anthropics/claude-plugins-official/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/skills/access/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/anthropics/claude-plugins-official/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/skills/access/SKILL.md Supports: upstreamDescription, review.notTested, review.reviewedAt
- [2026-10-15 W08 source re-review at the existing pin ↗](https://raw.githubusercontent.com/anthropics/claude-plugins-official/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/README.md) Checked 2026-10-15 https://raw.githubusercontent.com/anthropics/claude-plugins-official/41f32e407b450055044f167db7ded5e8ff67d203/external_plugins/telegram/README.md Supports: install.command

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Discord access ↗ Pins the Discord access skill, which refuses channel-originated allowlist edits and will not approve a pairing without its code.](/skills/anthropic-discord-access/)[### Telegram configure ↗ Pins the Telegram setup skill, which stores a bot token with mode 600 and says pairing should end once the allowlist is known.](/skills/anthropic-telegram-configure/)[### Discord configure ↗ Pins the Discord setup skill, which stores a bot token as a credential and treats pairing as temporary until the allowlist is locked.](/skills/anthropic-discord-configure/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
