Add Telegram channel integration via Chat SDK.
60
71%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/add-telegram/SKILL.mdSecurity
1 high severity finding. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill prompts the agent to capture user-supplied bot tokens and then injects those secrets verbatim into commands and requests (curl and CLI set-env), requiring the LLM/agent to output the secret values directly.
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
In SKILL.md, the runtime workflow includes a Telegram pairing step (setup/index.ts step “pair-telegram”) that will observe Telegram messages from the bot/chat to complete pairing, so outsider-authored free text can be ingested via chat input.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill runs curl against the Telegram API at runtime (curl -sf https://api.telegram.org/bot{{bot_token}}/getMe and curl -sf https://api.telegram.org/bot{{bot_token_2}}/getMe) and injects the returned JSON username into the setup flow and validation checks, so the external responses directly influence prompts/flow and are required for the skill to proceed.
b76fcb3
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.