Telegram CLI

**Overall**: Solid Telegram CLI well-suited for agent integration. It exposes the core messaging, search, and group/contact operations and supports JSON output on all commands, which is ideal for OpenClaw workflows. **Recommended scenarios** - When the user explicitly wants to **check or read Telegram messages**, including unread/inbox summaries. - When the user asks to **search Telegram chats** for past information (topics, links, decisions, etc.). - When the user asks to **send or reply to a Telegram message** to a specific user, group, or channel. - When the user needs **group/contact context** (members, admins, contact info, list of groups where they are admin). **Key strengths** - Comprehensive coverage of everyday Telegram operations: inbox, chats, read, search, send, reply, contacts, group members/admins, and session status. - Uniform `--json` output makes it easy and reliable for an LLM agent to parse and reason about results. - Clear, composable CLI interface with time and count filters (e.g., `-n 50`, `--since "1h"`). **Risks & caveats** - **Partial chat name matching** (e.g., "MetaDAO" matching "MetaDAO Community") can cause the agent to select the wrong chat when sending messages; agents should cross-check chat IDs/names from `tg chats --json` before sending. - Requires **Telegram API credentials and local authentication**, which must already be set up for the skill to operate; otherwise commands will fail. - Reliability and maintenance level are not fully known from the metadata; agents should handle command failures and validate outputs before taking follow-up actions.