access

Manage Telegram channel access via CLI with allowlist and policy edits.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/cjrfoto/claude-config --skill access-cjrfoto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: access
Source: https://github.com/cjrfoto/claude-config/tree/main/plugins/cache/claude-plugins-official/telegram/0.0.6/skills/access
Command: npx skills add https://github.com/cjrfoto/claude-config --skill access-cjrfoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Telegram channel access management is error-prone when done through scattered messages. This skill centralizes control by keeping all state in ~/.claude/channels/telegram/access.json and exposing a safe CLI interface to approve pairings, edit allowlists, and set DM/group policies without talking to Telegram directly.

Core Features & Use Cases

  • Approve pending pairings by validating pairing codes and updating allowlist.
  • Edit allowlists and set per-group access policies for channels.
  • Change policy modes (pairing, allowlist, disabled) and manage group configurations.

Quick Start

Approve a pairing by supplying the pending code to the command.

Frequently Asked Questions about access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Telegram channel access control and approve pairings via CLI?

Telegram channel access control is managed by running CLI commands to approve pending pairing codes, edit allowlists, and set DM or group policies. All state changes are written directly to the local access.json configuration file.

What is the best way to configure a Telegram allowlist without triggering channel notifications?

Configuring a Telegram allowlist safely requires using a CLI interface that reads and writes local state files directly. This approach prevents channel notifications from mutating access control state during policy updates.

How does pairing approval work for Telegram channels using a local access configuration?

Pairing approval works by validating a pending pairing code supplied to the CLI. Once validated, the sender ID is deduplicated and stored as an approved contact under the local telegram channel directory.

Can I change Telegram group and DM policies using a local JSON file instead of direct messaging?

Yes, you can change Telegram group and DM policies by updating the local access.json file via CLI. This allows switching between pairing, allowlist, and disabled policy modes without talking to Telegram directly.

Do I need a direct Telegram API connection to edit channel access policies and allowlists?

No, you do not need a direct Telegram API connection. The skill centralizes control by keeping all access state in a local JSON file and exposing a safe CLI interface to manage policies without communicating with Telegram directly.

Why are duplicate sender IDs causing issues when updating my Telegram channel allowlist?

Duplicate sender IDs cause allowlist conflicts when multiple pairing requests are approved. The access control process automatically deduplicates sender IDs before storing approved contacts to maintain a clean allowlist state.