Telegram Agent Setup V101
v1.0.1Complete guide to connecting OpenClaw with Telegram. Set up bot, configure channels, handle groups/topics, voice messages, inline buttons, media, and trouble...
⭐ 0· 33·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is an instruction-only guide to create a Telegram bot, configure OpenClaw, and enable STT via faster-whisper. All required steps (BotFather token, editing ~/.openclaw/openclaw.json, installing faster-whisper) align with that purpose.
Instruction Scope
Runtime instructions stay on-topic: creating the bot, editing OpenClaw config, examining logs, enabling group behavior, and installing a local STT package. The skill does not direct the agent to read unrelated system paths or exfiltrate data to third-party endpoints.
Install Mechanism
This is instruction-only (no install spec). The only installation recommended is a pip install of faster-whisper into a local venv, which is proportionate to the stated STT capability and uses a common package source.
Credentials
No platform environment variables or external credentials are requested by the registry metadata. The guide correctly asks the user to supply their Telegram bot token in the OpenClaw config file (not as an env var). This is proportionate, though users should follow secure storage practices.
Persistence & Privilege
The skill does not request always:true or system-wide privileges and is user-invocable only. It does not instruct modifying other skills or agent-wide settings beyond the agent's own OpenClaw config file.
Assessment
This guide appears coherent and appropriate for connecting OpenClaw to Telegram. Before following it: (1) Keep your bot token secret — do not commit ~/.openclaw/openclaw.json to source control or paste the token in chat; consider using a secrets manager if available. (2) Use the recommended venv for faster-whisper and verify you install packages from PyPI only. (3) Configure allowedChatIds and rejectUnknown:true to prevent unauthorized use. (4) Confirm outbound HTTPS access for the gateway and that logs do not leak secrets. (5) Verify the instructions against official OpenClaw documentation if available, and be cautious about contacting third-party helpers listed in the README.Like a lobster shell, security has layers — review code before you run it.
latestvk974w0ec65rk93zy0k6wjpvhw1846fs1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
