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

69%

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.

The content is well-structured, concrete, and actionable with specific tool sequences and limits, but destructive/batch workflows lack validation feedback loops and some content is duplicated across sections. Adding verify-then-proceed steps and de-duplicating pitfalls would raise the score.

Suggestions

Add explicit validation checkpoints to destructive workflows, e.g. before DELETE_MESSAGE confirm the message_id and chat_id, and after sending verify delivery; add a 429-retry/backoff feedback loop for batch sends.

De-duplicate pitfalls: keep them either in each workflow or in 'Known Pitfalls', not both, to reduce token cost.

Consider moving the Quick Reference table and consolidated limits into a separate reference file to slim the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but pitfalls are duplicated between per-workflow 'Pitfalls' blocks and the 'Known Pitfalls' section, and the Quick Reference table repeats tool/param info already listed in workflows.	4 / 5
Actionability	Concrete numbered tool sequences with [Prerequisite]/[Required]/[Optional] tags, exact parameter names, and precise limits (4096 chars, 1024 caption, 50MB) give highly actionable guidance; it stops short of literal copy-paste commands, but tool-call sequences are the executable unit for this MCP skill.	4 / 5
Workflow Clarity	Sequences are clearly numbered, but destructive workflows (edit/delete messages) and batch/rate-limited operations lack explicit validation checkpoints or verify-then-proceed feedback loops, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The doc is well-organized with clear section headers and a navigation-friendly structure and needs no external references, but at ~225 lines the Quick Reference table and consolidated pitfalls could be split out to tighten the overview.	4 / 5
	Total	15 / 20 Passed

Description

70%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.

The description is specific, action-oriented, and clearly distinctive, but it omits an explicit 'Use when' trigger clause, which caps completeness. Adding trigger guidance would lift the completeness and trigger-term scores.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to send or manage Telegram messages, share media, or configure bot commands.'

Expand action coverage to mention forwarding, fetching updates, and editing/deleting messages for more comprehensive specificity.

Include natural synonyms users say such as 'Telegram bot' and file/media terms to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and four concrete action areas ('send messages, manage chats, share photos/documents, and handle bot commands'), but omits several Telegram capabilities like forwarding, updates, and message editing so coverage has minor gaps rather than being comprehensive.	4 / 5
Completeness	It clearly states what the skill does but lacks any explicit 'Use when...' trigger clause; per the rubric guideline a missing explicit trigger caps completeness at 3 even though the 'what' is clear.	3 / 5
Trigger Term Quality	Includes natural user-facing terms like 'Telegram', 'send messages', 'share photos/documents', and 'bot commands', but misses common variations such as 'Telegram bot', 'forward messages', or 'get updates'.	4 / 5
Distinctiveness Conflict Risk	The 'Telegram via Rube MCP (Composio)' framing carves out a clear niche with distinct triggers and minimal overlap risk with other communication skills.	5 / 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: a9fa86d

Reviewed: about 19 hours 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.