Telegram Readonly

Read the user's personal Telegram account in a controlled, read-only way via Telethon/MTProto. Use when you need to inspect Telegram chats, list dialogs, rea...

This skill implements a read-only Telethon client and legitimately needs TELEGRAM_API_ID, TELEGRAM_API_HASH, and a session string; however the registry metadata does not declare those env vars — that's an inconsistency you should not ignore. Before installing: (1) inspect the upstream GitHub repo (https://github.com/ropl-btc/telegram-readonly-cli) — review code, recent commits, open issues, and releases; (2) prefer cloning and reviewing locally before pipx installing; (3) do not provide your session string or credentials to untrusted agents or services; use the interactive auth flow and protect ~/.config/telegram-readonly/config.json (permission 600 is set by the script); (4) avoid exposing TELEGRAM_SESSION_STRING via environment to other processes/agents that could read env vars; (5) consider disabling autonomous invocation for agents that will have access to these credentials or run the skill only under direct user control. The metadata mismatch lowers trust — resolve that (ask the publisher to declare required env vars) before granting the skill access to your Telegram credentials.

Type: OpenClaw Skill Name: telegram-readonly Version: 0.1.2 The skill provides a specialized read-only interface for accessing a personal Telegram account via the Telethon library. The implementation in `scripts/telegram_readonly.py` is well-structured, lacks any write operations (send/delete/edit), and follows security best practices by enforcing restricted file permissions (chmod 600) on the configuration file containing sensitive session strings. The documentation in `SKILL.md` and `setup-and-safety.md` explicitly defines the safety model and warns the user about the high-privilege nature of MTProto sessions, aligning perfectly with the stated purpose without any signs of malicious intent or obfuscation.