Relay for Telegram
PassAudited by ClawScan on May 10, 2026.
Overview
The visible artifacts show a coherent, read-only Telegram history integration, but installing it means trusting Relay with synced private messages and allowing the agent to query them for Telegram-related requests.
Install only if you are comfortable letting Relay sync and store selected Telegram message history and letting the agent query it for Telegram-related tasks. Keep `RELAY_API_KEY` private, consider disabling model invocation for explicit control, and limit synced chats if possible.
Findings (4)
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.
If configured, the agent may search synced Telegram history when it interprets a request as Telegram-related.
The skill permits model-initiated read-only queries for Telegram-related requests. This is disclosed and includes opt-out guidance, but it affects user control over when private messages are searched.
This skill has `disable-model-invocation: false`, meaning the AI agent can use it on its own initiative when it determines a request is Telegram-related — without requiring you to explicitly invoke it each time.
Set `disable-model-invocation: true` or unset `RELAY_API_KEY` if you want to approve each use explicitly.
Anyone or any agent session with the API key may be able to read the Telegram messages that Relay has synced.
The skill requires a Relay API key obtained through Telegram verification, which grants access to synced Telegram message data. This credential use is expected for the stated purpose and is described as read-only.
To enable it, you must: ... Complete Telegram phone verification to get an API key ... Set `RELAY_API_KEY` as an environment variable.
Protect the API key, use this only if you trust Relay, and revoke/unset the key when you no longer want the agent to access synced messages.
Private Telegram content may be surfaced, summarized, or reasoned over by the agent.
The skill retrieves stored Telegram message history into the agent’s context. This is central to the purpose and includes disclosed storage protections, but it can expose private chat content during agent sessions.
The agent can search and read your synced messages ... All messages are encrypted at rest using AES-256-GCM.
Limit which chats are synced where possible, avoid syncing highly sensitive conversations, and treat retrieved chat text as user data rather than trusted instructions.
Users must rely on the hosted Relay service’s stated privacy and security behavior without source review from these artifacts.
No local code or install script is shown, so there is no install-time execution concern in the provided artifacts. However, the hosted service source/provenance is not available in the supplied metadata.
Source: unknown
Review Relay’s public documentation and privacy policy before connecting a Telegram account or syncing sensitive chats.