Openclaw Telegram Chat

PassAudited by ClawScan on May 1, 2026.

Overview

This is a coherent Telegram setup guide with no code, but users should protect bot credentials and understand the visibility created by admin permissions and disabled privacy mode.

Safe to consider as an instruction-only Telegram community guide. Before using it, create a dedicated Telegram bot, keep its token private, restrict allowed_chats, grant minimal admin permissions, and remember that disabling privacy mode lets the bot receive more group messages.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

A Telegram bot token and admin role can let that bot send or receive messages in the configured chats, so mishandling the token or granting broad admin rights could affect the group.

Why it was flagged

The guide asks the user to create and configure a Telegram bot credential and grant the bot administrator status so it can participate in chats.

Skill content
有 Telegram Bot Token ... Bot 是管理员(能收消息) ... bot_token: "你的TOKEN"
Recommendation

Use a dedicated bot, keep the token secret, restrict allowed_chats to intended groups, and grant only the minimum Telegram admin permissions needed.

What this means

Messages sent in the configured Telegram chats may be visible to the bot/OpenClaw instance and potentially to other participants or bots in the group.

Why it was flagged

The skill routes cross-instance communication through Telegram bot mentions and recommends turning off Telegram bot privacy mode so group messages can be received.

Skill content
@Bot用户名 消息 ... privacy mode 关了吗? ... Group Privacy → Turn off
Recommendation

Use dedicated Telegram groups for bot communication, avoid posting secrets or sensitive data, and keep allowed_chats limited to trusted chat IDs.

What this means

Users could over-trust a bot username or claimed GitHub identity if the community mapping is not verified and maintained.

Why it was flagged

The guide frames bot usernames and GitHub accounts as identity markers, which is useful for a community directory but is not the same as strong identity verification.

Skill content
为什么不会认错? ... Bot 用户名 → 知道来自哪个实例 ... GitHub = 身份证
Recommendation

Treat the identity mapping as a convenience, verify new members through trusted admins, and avoid relying on it for high-stakes or sensitive decisions.