CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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.md

The canonical home for this skill is telegram-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 body delivers concrete, well-structured MCP-tool guidance with genuine operational knowledge (limits, escaping, permissions, rate limits). Its weaknesses are duplicated pitfall/limit facts across sections, missing validation steps around the destructive delete and bulk-send workflows, and a useless tautological closing section.

Suggestions

Add a validation step before destructive operations, e.g. verify the correct chat_id/message_id with TELEGRAM_GET_CHAT_HISTORY before TELEGRAM_DELETE_MESSAGE, and describe a 429 retry-with-delay loop for bulk sends.

Deduplicate repeated facts: state character limits, MarkdownV2 escaping, and bot-permission rules once (in "Known Pitfalls") and remove them from individual workflow sections.

Delete or replace the tautological "When to Use" section ("applicable to execute the workflow or actions described in the overview") with a short list of concrete triggering scenarios.

DimensionReasoningScore

Conciseness

The body is mostly dense, non-obvious operational detail (limits, escaping rules, rate limits), but several facts are stated twice: MarkdownV2 escaping appears in "Send Messages" pitfalls and again in "Message Formatting", the 4096/1024-char and 50MB limits appear in both workflow pitfalls and "Known Pitfalls", and bot-permission rules are repeated three times. The closing "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview") is pure filler, matching the anchor of mostly efficient with some unnecessary content that could be tightened.

3 / 5

Actionability

Concrete tool slugs (TELEGRAM_SEND_MESSAGE, TELEGRAM_SET_MY_COMMANDS), numbered sequences with [Required]/[Optional]/[Prerequisite] markers, explicit parameters, and a task-to-tool Quick Reference table give mostly executable guidance. It is not a 5 because no example tool-call payloads or argument snippets are shown, only parameter names.

4 / 5

Workflow Clarity

Sequences are clearly ordered with per-workflow "When to use" guidance and a setup verification checkpoint ("Confirm connection status shows ACTIVE before running any workflows"). However, the destructive TELEGRAM_DELETE_MESSAGE workflow proceeds with no validation of the target message_id, and bulk sends are mentioned ("Bulk operations should implement delays") without any verify-then-retry loop, so the destructive/batch cap of 3 applies despite otherwise solid sequencing.

3 / 5

Progressive Disclosure

No bundle files exist, and the single SKILL.md is well-organized with clear section headers, per-workflow subsections, and an at-a-glance Quick Reference table, giving good structure with only minor organization gaps. It is not a 5 because the 200+ line body inlines detailed pitfalls and a full tool table that could optionally be split into a reference file, though the single-file layout remains navigable.

4 / 5

Total

14

/

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 concrete, appropriately concise, and clearly anchored to a distinct Telegram-automation niche. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness, and its action list omits a few capabilities the skill body actually covers.

Suggestions

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

Broaden natural trigger terms to include "channel", "group", "forward", and "file" so common user phrasings match.

Mention one or two more covered actions (e.g., "edit and delete messages") to close the coverage gap with the skill body.

DimensionReasoningScore

Specificity

"send messages, manage chats, share photos/documents, and handle bot commands" lists several concrete, specific actions, matching the anchor for several specific actions with minor gaps. It is not a 5 because capabilities covered in the body (edit/delete messages, forwarding, invite links) are omitted from the description.

4 / 5

Completeness

The description clearly answers "what" ("Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands") but contains no "Use when..." trigger clause; "Always search tools first for current schemas" is an instruction to the agent, not usage guidance. Per the judging guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like "Telegram", "send messages", "photos/documents", and "bot commands" align with what users would actually say, giving good keyword coverage. It falls short of 5 because common variations such as "channel", "group", "forward", and "file" are missing.

4 / 5

Distinctiveness Conflict Risk

"Telegram" combined with "Rube MCP (Composio)" carves out a clear niche with distinct triggers and minimal conflict risk against other skills. The Telegram-specific vocabulary makes mistaken triggering for a non-Telegram skill unlikely.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/telegram-automation/SKILL.md

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.