telegram-automation
Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas.
53
60%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/telegram-automation/SKILL.mdThe canonical home for this skill is telegram-automation in administrakt0r/AI-Agents-Safe-Coding-Skills
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
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.
Why it was flagged
SKILL.md describes Telegram tool workflows (e.g., TELEGRAM_SEND_MESSAGE) where the runtime ingests user-supplied `text`/`caption` parameters to send or edit messages, meaning outsider-authored free text can flow directly into the LLM-controlled workflow.
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
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.
Why it was flagged
The skill explicitly requires adding https://rube.app/mcp as an MCP server and instructs calling RUBE_SEARCH_TOOLS at runtime to fetch tool schemas, meaning this external endpoint is used during runtime to provide instructions/schema that directly control agent behavior.
- Commit
fbdfd63
- Audited
- Security analysis
Is this your skill?
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.