Relay for Telegram
Analysis
This skill appears coherent and read-only, but it deserves careful review because it lets an agent query private Telegram message history through a third-party API and may do so automatically for Telegram-related requests.
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
disable-model-invocation: false ... the AI agent can use it on its own initiative when it determines a request is Telegram-related
The skill allows automatic model-initiated access for relevant requests instead of requiring the user to invoke the skill every time.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
requires: {"env":["RELAY_API_KEY"]} ... Complete Telegram phone verification to get an API keyThe skill requires a Relay API key obtained through Telegram phone verification, giving the agent delegated read access to the user's synced Telegram data.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
The agent can search and read your synced messages ... Syncing happens ... during login, when you manually sync a chat, or via periodic background sync
The skill relies on a persistent synced message store and returns Telegram message content into the agent's context for search and summarization.
