← 返回 Skills 市场

Telegram - Full Access

Name: Telegram - Full Access
Author: seichris

作者 Chris · GitHub ↗ · v1.0.0 · MIT-0

cross-platform ✓ 安全检测通过

总下载

当前安装

版本数

在 OpenClaw 中安装

/install telegram-full-access

功能描述

Give OpenClaw full access to your Telegram: Log into a local Telegram session, use a personal or dedicated account, let Claw automate your workflows, and man...

使用说明 (SKILL.md)

telegram-full-access

Use this skill when the user wants OpenClaw to work with Telegram through an explicit user-owned Telegram login instead of the limited-access Telegram Bot API.

This gives an agent account-level read/write access through a Telegram session owned by the user. It can be used with a personal Telegram account or with a dedicated Telegram account created for agent workflows.

What This Sets Up

A local Telegram session controlled by the user.
Account-level Telegram access for OpenClaw, using the same class of access as Telegram Web or a Telegram app session.
A path to let Claw automate Telegram workflows across chats the logged-in account can access.
A CRM UI path through Chiho.ai for managing chats, contacts, tags, tasks, summaries, and follow-ups.

Why Not Bot Access

Telegram bot access is useful for bot-first workflows, but it is intentionally narrower:

Bots must be manually added to chats.
Bots do not automatically see a user's existing Telegram inbox.
Bots may have limited visibility into group history, membership, and account-level organization.

Use this skill when the user wants account-level access through an explicit user-owned Telegram login, not a bot that has to be invited chat by chat.

Choose A Runtime

Chiho.ai Cloud

Use Chiho.ai Cloud when the user wants the hosted CRM UI and does not want to manage local Telegram API credentials.

Open Chiho.ai.
Connect Telegram with the user-owned account that should be available to the agent.
Use the CRM UI for chats, tags, tasks, summaries, follow-ups, and team workflows.
Mint an Agent Access token from https://chiho.ai/profile/agent-access.
Connect OpenClaw or another MCP client to https://api.chiho.ai/mcp.

Prefer this path when the user wants the CRM UI, hosted session management, or the quickest setup.

Self-Hosted `tgchats`

Use the local tgchats runtime when the user explicitly wants self-hosting or local data ownership.

Clone telegram-for-ai-agents.
Configure Telegram API credentials from https://my.telegram.org/apps:
- TELEGRAM_API_ID
- TELEGRAM_API_HASH
Configure optional CRM storage with DATABASE_URL.
Run local setup:

npm install
cp .env.example .env
npm run dev -- auth
npm run mcp

After login, prefer MCP tools exposed by tgchats-mcp. Fall back to tgchats --json only when MCP is unavailable.

Operating Rules

The Telegram session must be created by the user who controls the account.
A dedicated Telegram account is recommended when the user wants clearer boundaries for agent workflows.
Do not claim access to chats the logged-in account cannot normally access.
Do not automate message sending unless the user has explicitly enabled a write-capable workflow and approved the action.
Use the CRM UI path when the user asks for table-based chat management, tags, tasks, summaries, or follow-up workflows.

Related Links

安全使用建议

Install only if you are comfortable giving an agent account-level Telegram access. Prefer a dedicated Telegram account for automation, review Chiho.ai’s privacy and retention terms before using the cloud path, and keep write-capable workflows disabled unless you intend the agent to send messages.

能力标签

requires-oauth-tokenrequires-sensitive-credentials

能力评估

ℹ Purpose & Capability

The stated purpose is account-level Telegram access, including read/write automation and CRM workflows; that is high-impact but coherent with the skill name, description, and operating rules.

ℹ Instruction Scope

The skill limits sending messages to explicitly enabled write-capable workflows with user approval, but it could more prominently explain that account-level access may expose all chats available to the logged-in account.

✓ Install Mechanism

The artifact is a single SKILL.md with setup instructions only; no executable payload, hidden installer, obfuscated command, or automatic mutation was found.

ℹ Credentials

Telegram API credentials, a local session, optional database storage, and a hosted Chiho.ai path are proportionate to the full-access Telegram/CRM purpose, though the hosted path deserves careful privacy review.

ℹ Persistence & Privilege

The skill intentionally creates a persistent Telegram session or hosted agent token, but this is disclosed as part of the setup and tied to user-controlled account access.

如何使用

确保已安装 OpenClaw（本地或 Docker 部署）
在对话框中输入安装命令：/install telegram-full-access
安装完成后，直接呼叫该 Skill 的名称或使用 /telegram-full-access 触发
根据 Skill 的参数说明提供必要输入，即可获得结构化输出

版本历史

v1.0.0

Initial release of telegram-full-access. - Enables OpenClaw to access Telegram via a full user session, not just the Bot API. - Supports both personal and dedicated Telegram accounts for agent workflows. - Offers two deployment modes: Chiho.ai Cloud (with CRM UI) and self-hosted local runtime. - Provides CRM capabilities for managing chats, contacts, tags, tasks, summaries, and follow-ups. - Optional environment variables for Telegram API and CRM database integration.

元数据

Slug telegram-full-access

版本 1.0.0

许可证 MIT-0

累计安装 1

当前安装数 1

历史版本数 1

常见问题