Relay for Telegram
v1.0.4The best way to access Telegram message history. Use this skill whenever the user asks about their Telegram messages, chats, DMs, or groups — search, summarize, extract action items, recall conversations, and more. Provides a production-ready API for querying synced Telegram data. Also available as a ChatGPT App via MCP.
⭐ 7· 2.3k·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is described as a read-only relay for synced Telegram history and only requires a single API key (RELAY_API_KEY). The metadata points to relayfortelegram.com and the SKILL.md shows API calls to that domain; there are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
The SKILL.md instructs the agent to query the Relay API and to have the user obtain and set RELAY_API_KEY. It does not direct the agent to read local files, other environment variables, or system credentials, nor to transmit data to unexpected endpoints. The skill documents that access is read-only and previously-synced only.
Install Mechanism
This is an instruction-only skill with no install spec or code files, so nothing is downloaded or written to disk by the skill itself. Example setup steps use HTTPS curl calls to relayfortelegram.com (a reasonable, expected pattern).
Credentials
Only RELAY_API_KEY is required and is declared as the primary credential; that aligns with the service's purpose (an API key to query a user's synced Telegram data). No additional unrelated secrets or config paths are requested.
Persistence & Privilege
Model invocation is enabled by default (disable-model-invocation: false), meaning the agent may autonomously query Relay when it detects Telegram-related requests. This is consistent with the advertised UX but is a privacy decision users should consider — the skill itself does not request elevated system privileges or 'always' installation.
Assessment
This skill appears coherent and only needs a single API key to read your synced Telegram history. Before installing: 1) Verify you trust relayfortelegram.com (check reputation, privacy policy, and TLS certificate). 2) Use a limited or ephemeral API key if possible and only sync the chats you want Relay to see. 3) If you prefer manual control, set disable-model-invocation: true so the agent won't query your messages automatically. 4) Remove the RELAY_API_KEY from your environment when not using the skill. 5) Confirm the sign-in flow doesn't require sharing your Telegram account password with a third party (the doc claims 2FA is forwarded to Telegram and not stored). If any of these checks fail or you cannot verify the service, do not install the skill.Like a lobster shell, security has layers — review code before you run it.
latestvk97eqfbktjztwjwt3r6496v20s80xy64
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
⚡ Clawdis
EnvRELAY_API_KEY
Primary envRELAY_API_KEY