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.
87
Quality
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 excels across all dimensions. It provides specific actions, includes natural trigger terms users would use, explicitly states both what the skill does and when to use it with a clear 'Use when...' clause, and targets a distinct niche (Telegram bots for OpenClaw) that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'bot registration, token validation, network connectivity checks', plus 'setting up Telegram integrations, troubleshooting bot connectivity, configuring bot tokens, managing Telegram channel/webhook settings'. | 3 / 3 |
Completeness | Clearly answers both what ('Manage and configure Telegram bots', 'bot registration, token validation, 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 natural keywords users would say: 'Telegram bots', 'bot tokens', 'webhook settings', 'Telegram channel', 'api.telegram.org', 'bot connectivity'. Good coverage of terms a user working with Telegram integrations would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Telegram bots for OpenClaw specifically. The combination of 'Telegram', 'OpenClaw', 'api.telegram.org', and bot-specific terminology makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable guidance for Telegram bot management with good structure and clear references. The main weaknesses are some unnecessary explanations of concepts Claude already knows (BotFather commands, webhook vs polling basics) and missing validation checkpoints in workflows that could benefit from explicit verification steps.
Suggestions
Remove or condense the Bot Commands Reference section - these are standard BotFather commands Claude can look up
Add explicit validation steps to the setup workflow (e.g., 'Verify bot responds before proceeding to OpenClaw config')
Trim the Webhook vs Polling section to just the reference link since Claude understands these concepts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary content like explaining what BotFather is and basic concepts Claude would know. The bot commands reference section lists standard BotFather commands that are easily discoverable. | 2 / 3 |
Actionability | Provides concrete, executable curl commands for testing connectivity and token validation. Setup steps are specific with clear format examples for tokens. Commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | Troubleshooting steps are clearly sequenced, but lacks explicit validation checkpoints and feedback loops. The setup workflow doesn't specify how to verify successful configuration before proceeding. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate references to external files (OPENCLAW_CONFIG.md, WEBHOOK_SETUP.md). Content is organized logically with quick start, common workflows, and references clearly separated. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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.
45f9fac
Table of Contents
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.