telegram-bot-manager

Manage and configure Telegram bots for OpenClaw. Use when setting up Telegram integrations, troubleshooting bot connectivity, configuring bot tokens, or managing Telegram channel/webhook settings. Handles bot registration, token validation, and network connectivity checks for api.telegram.org.

Quality

75%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/362224222/telegram-bot-manager/SKILL.md

Quality

Discovery

100%

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

This is a well-crafted skill description that clearly defines its scope (Telegram bot management for OpenClaw), provides explicit trigger conditions via a 'Use when...' clause, and lists specific concrete actions. It uses proper third-person voice throughout and includes domain-specific terms that would naturally appear in user requests.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: bot registration, token validation, network connectivity checks, configuring bot tokens, managing webhook settings. These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers both what ('Manage and configure Telegram bots', 'Handles bot registration, token validation, and network connectivity checks') and when ('Use when setting up Telegram integrations, troubleshooting bot connectivity, configuring bot tokens, or managing Telegram channel/webhook settings').	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Telegram bots', 'bot tokens', 'webhook settings', 'Telegram channel', 'bot connectivity', 'api.telegram.org'. Good coverage of terms a user troubleshooting or setting up Telegram integrations would use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Telegram bot management specifically for OpenClaw. The combination of 'Telegram', 'OpenClaw', 'api.telegram.org', and bot-specific terminology makes it very unlikely to conflict with other skills.	3 / 3
	Total	12 / 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.

The skill provides a reasonable overview of Telegram bot management for OpenClaw with some executable commands, but suffers from vagueness in the most critical steps (actual OpenClaw configuration) and includes generic knowledge Claude already possesses (BotFather commands, webhook vs polling concepts). The referenced bundle files don't exist, undermining the progressive disclosure structure.

Suggestions

Replace the vague 'Add token to OpenClaw config / Enable Telegram plugin' steps with specific config file paths, key names, and example configuration snippets

Remove or significantly trim the BotFather commands reference and webhook vs polling explanation—these are well-known concepts that don't need to live in the skill body

Add an explicit validation checkpoint after bot setup (e.g., a curl command or script that confirms the bot is properly connected to OpenClaw)

Create the referenced bundle files (references/OPENCLAW_CONFIG.md, references/WEBHOOK_SETUP.md) or remove the broken references

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanations Claude would already know (e.g., explaining what webhooks vs polling are, listing basic BotFather commands that are easily discoverable). The bot token security section is generic advice. However, it's not egregiously verbose—most sections are reasonably sized.	2 / 3
Actionability	The curl commands for connectivity testing and token validation are concrete and executable. However, key steps like 'Add token to OpenClaw config' and 'Enable Telegram plugin' are vague with no specific file paths, config keys, or code. The 'automated testing' section references a script that may not exist. Several sections describe rather than instruct.	2 / 3
Workflow Clarity	The troubleshooting connectivity workflow has clear numbered steps with commands, but lacks validation checkpoints and feedback loops. The setup workflow is sequential but step 2 ('Configure in OpenClaw') is too vague to be actionable. There's no explicit 'verify success' step after setup—no validation that the bot is actually connected and working before proceeding.	2 / 3
Progressive Disclosure	The skill references OPENCLAW_CONFIG.md and WEBHOOK_SETUP.md for detailed content, which is good structure. However, no bundle files are provided, so these references may be broken. The BotFather commands list and webhook vs polling explanation could arguably be in reference files rather than inline, as they pad the main skill without being core workflow content.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Demerzels-lab/elsamultiskillagent
Commit: f45fcb5

Reviewed: 12 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.