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.
71
58%
Does it follow best practices?
Impact
91%
1.68xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/telegram-automation/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is strong in specificity and distinctiveness, clearly naming the platform (Telegram), the integration mechanism (Rube MCP/Composio), and concrete actions. However, it lacks an explicit 'Use when...' clause which caps completeness, and could benefit from additional natural trigger terms users might employ when requesting Telegram-related tasks.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to send Telegram messages, interact with Telegram bots, or automate Telegram workflows.'
Include additional natural trigger terms like 'Telegram bot', 'TG', 'post to Telegram', 'Telegram notification', or 'Telegram API' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'send messages, manage chats, share photos/documents, and handle bot commands.' Also includes the operational instruction to 'search tools first for current schemas.' | 3 / 3 |
Completeness | Clearly answers 'what' (send messages, manage chats, share photos/documents, handle bot commands via Rube MCP/Composio), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The triggers are only implied by the action list. | 2 / 3 |
Trigger Term Quality | Includes good keywords like 'Telegram', 'send messages', 'photos/documents', 'bot commands', but misses common user variations like 'Telegram bot', 'TG', 'chat message', 'Telegram API', or specific action terms users might say like 'post to Telegram' or 'Telegram notification'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform (Telegram), specific integration (Rube MCP / Composio), and specific actions. Unlikely to conflict with other skills unless there's another Telegram skill. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent but verbose skill that covers Telegram automation comprehensively. Its main strengths are clear workflow sequencing with Required/Optional annotations and a useful quick reference table. Its weaknesses are significant redundancy (pitfalls and limits repeated multiple times), lack of executable examples showing actual MCP call syntax, and missing validation/error-recovery steps in workflows.
Suggestions
Add at least one concrete, executable example showing an actual RUBE_SEARCH_TOOLS call followed by a TELEGRAM_SEND_MESSAGE call with real parameter syntax, so Claude knows the exact invocation format.
Remove duplicated pitfall information—consolidate character limits, file size limits, and permission requirements into the 'Known Pitfalls' section only, and reference it from individual workflows instead of repeating.
Add validation/error-recovery steps to workflows, especially for send operations (e.g., check response for success, handle 429 rate limit errors with retry logic, verify message_id in response).
Consider splitting the detailed per-workflow pitfalls and parameter references into a separate REFERENCE.md file to keep SKILL.md as a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but contains significant redundancy—pitfalls are repeated across individual workflows and then again in a consolidated 'Known Pitfalls' section (e.g., 4096 char limit, 1024 caption limit, 50MB file limit appear multiple times). The quick reference table also duplicates information already covered. Some content like chat type definitions is general Telegram knowledge Claude already possesses. | 2 / 3 |
Actionability | The skill provides tool names, parameter lists, and tool sequences, which is useful. However, there are no executable code examples or concrete MCP call examples showing actual invocation syntax with real parameters. The 'Common Patterns' section uses pseudocode-style numbered steps rather than actual executable calls. A user/Claude would need to call RUBE_SEARCH_TOOLS anyway to get schemas, reducing the actionability of the parameter listings. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps and labeled as Required/Optional, which is good. However, there are no validation checkpoints or error recovery steps within the workflows—no guidance on what to do if TELEGRAM_SEND_MESSAGE fails, no verification that a message was actually sent, and no feedback loops for handling rate limit errors (429 responses) despite mentioning them in pitfalls. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's quite long (~180 lines of substantive content) with no bundle files to offload detailed reference material. The pitfalls, parameter details, and workflow specifics could be split into separate reference files. The single external link to Composio docs is appropriate but the skill itself is monolithic. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
c911a92
- Reviewed
Table of Contents
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.