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.

1.68x

Quality

70%

Does it follow best practices?

Impact

91%

1.68x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/telegram-automation/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable reference with concrete tool sequences, parameters, and pitfalls that appropriately assumes Claude's competence. Its main weaknesses are missing validation/feedback steps around destructive (delete) and batch operations — which caps workflow clarity — and some duplicated limits/pitfalls across sections.

Suggestions

Add explicit validation to destructive and batch workflows, e.g. "Before TELEGRAM_DELETE_MESSAGE, confirm chat_id and message_id with the user; after bulk sends, check for 429 responses and retry with the returned retry_after delay."

Deduplicate the repeated limits (4096/1024-char, 50MB, MarkdownV2 escaping) by keeping them only in Known Pitfalls and referencing that section from the workflows.

Move the Quick Reference table and per-workflow pitfalls into a single reference file (e.g. references/tool-catalog.md) to shorten SKILL.md and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and factual — tool sequences, parameters, and pitfalls with no explanation of concepts Claude already knows. However, several facts are stated twice (MarkdownV2 escape characters, the 4096/1024-char and 50MB limits appear in both workflow pitfalls and Known Pitfalls, and the Quick Reference table partially restates the sequences), so minor trimming is possible. It is not 5 because of this duplication, and not 3 since the padding is limited and localized rather than pervasive.	4 / 5
Actionability	Concrete, executable guidance throughout: exact tool slugs ("TELEGRAM_SEND_MESSAGE"), [Required]/[Optional] tags, and literal parameter values ('@channelname', 'HTML', the escape character list). It falls short of fully copy-paste-ready because no example tool-call payloads are shown, relying on "Always call RUBE_SEARCH_TOOLS first" to fetch schemas.	4 / 5
Workflow Clarity	Each workflow is clearly numbered with prerequisites, and Setup includes an explicit checkpoint ("Confirm connection status shows ACTIVE before running any workflows"). However, the destructive delete-message workflow and the bulk/rate-limit guidance ("Bulk operations should implement delays between calls") lack validation or verification steps, and there are no validate-fix-retry feedback loops — per the judging guidelines this caps workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the single 225-line file is well-organized with clear section headers, a Common Patterns section, and an inline Quick Reference table. It is not 5 because the file exceeds the simple-skill threshold and the pitfalls catalog / quick reference table could be split into a one-level-deep reference file, though the current inline placement does not seriously impede navigation.	4 / 5
	Total	15 / 20 Passed

Description

71%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, third-person description that clearly states what the skill does with concrete named actions, but it omits any "Use when..." trigger guidance, which caps completeness and slightly weakens trigger-term quality and distinctiveness. Adding an explicit trigger clause would move it into the top band.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to send Telegram messages, share photos or files in a chat, manage chats, or configure bot commands."

Include common user phrasings and synonyms such as "forward messages", "channels", or "DM" to broaden natural trigger coverage.

Drop or compress "Always search tools first for current schemas" (it belongs in the body's Prerequisites, where it already appears) to keep the description focused on what/when.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — "send messages, manage chats, share photos/documents, and handle bot commands" — which comprehensively cover the skill's workflows. This matches the anchor for multiple specific concrete actions with comprehensive coverage, and exceeds the 'several specific actions with minor gaps' anchor.	5 / 5
Completeness	The "what" is clear ("Automate Telegram tasks... send messages, manage chats, share photos/documents"), but there is no "Use when..." clause or equivalent explicit trigger guidance — "Always search tools first for current schemas" is behavioral instruction, not a trigger. Per the judging guidelines, a missing trigger clause caps completeness at 3; it is not 4 because the "when" is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	Natural terms like "Telegram", "send messages", "photos/documents", and "bot commands" are present and would be said by users. A few common variations are missing (e.g., "file", "forward", "channel", "DM"), so it falls just short of the comprehensive-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	"Telegram" and "Rube MCP (Composio)" name a clear, specific niche. Minor overlap risk remains with closely related messaging skills (e.g., Slack or WhatsApp toolkits) since no explicit triggers distinguish usage; it is not 5 because the anchor's clear distinct triggers are absent, and not 3 because the domain is far more specific than generic document/file phrasing.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/telegram-automation/SKILL.md
Commit: c9856ea

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.