telegram-automation

SUSPICIOUS: the core Telegram capabilities match the stated purpose, and the required bot token is proportionate, but the skill relies on a discontinued Rube/Composio MCP path with outdated meta-tool names and stale tool references. Data flows through Composio-managed infrastructure rather than directly from the agent to Telegram, which is coherent for an MCP integration but introduces third-party trust and version-drift risk.