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 does a good job listing specific Telegram automation capabilities and is highly distinctive due to the platform and tooling specificity. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know when to select it, and the trigger terms could better cover natural user language variations.
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 more natural trigger term variations such as 'Telegram bot', 'TG', 'Telegram API', or 'Telegram notification' to improve matching with user requests.
| 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 does this do' with specific actions, but lacks an explicit 'Use when...' clause. There is no guidance on when Claude should select this skill over others. | 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'. The mention of 'Rube MCP (Composio)' is technical jargon users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Telegram' and 'Rube MCP (Composio)' creates a very clear niche. It's unlikely to conflict with other skills since Telegram automation via a specific MCP tool is highly distinctive. | 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 solid, well-organized skill that covers Telegram automation comprehensively with clear tool sequences and parameter documentation. Its main weaknesses are redundancy across sections (pitfalls repeated in workflows and in a dedicated section), lack of concrete executable examples showing actual MCP tool invocations, and missing validation/error-recovery steps in workflows. The content would benefit from trimming duplicated information and adding explicit verification checkpoints.
Suggestions
Add concrete, executable examples showing actual RUBE_SEARCH_TOOLS and TELEGRAM_SEND_MESSAGE invocations with real parameter structures, rather than just listing parameter names.
Add explicit validation checkpoints to workflows, e.g., 'After TELEGRAM_SEND_MESSAGE, check the response for ok:true and store the returned message_id for potential edits/deletes.'
Consolidate pitfalls into the dedicated 'Known Pitfalls' section and remove duplicated pitfall entries from individual workflow sections to reduce token usage.
Consider splitting the detailed workflow sections and quick reference table into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy—pitfalls are repeated across individual workflows and then again in the 'Known Pitfalls' section (e.g., message character limits, caption limits, bot permissions). The quick reference table duplicates information already covered. Some trimming would improve token efficiency. | 2 / 3 |
Actionability | The skill provides clear tool names, parameter lists, and sequenced steps, which is good. However, it lacks executable code examples—the 'Common Patterns' section uses pseudocode-like plain text blocks rather than actual API calls or concrete invocation examples showing exact parameter structures. Since the instruction says to always call RUBE_SEARCH_TOOLS first for current schemas, the lack of concrete call examples is partially justified but still leaves gaps. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps and labeled as Required/Optional, which is helpful. However, there are no explicit validation checkpoints or error recovery feedback loops—no 'if this fails, do X' patterns except the setup section. For operations like sending messages to chats where the bot might not have access, there's no verify-then-proceed pattern with error handling. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's quite long (~180 lines of substantive content) and monolithic. The pitfalls, common patterns, and detailed workflow sections could be split into separate reference files. The only external reference is the Composio toolkit docs link. For a skill this comprehensive, better use of linked sub-documents would improve navigation. | 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
7cc63f3
- 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.