AD telegram-bot
Create and manage Telegram bots. Use when user wants to build a Telegram bot for notifications, automation, customer support, group management, or interactive commands.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
GeneratorTelegramInfrastructureCustomer supporttype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (telegram-bot) differs from the folder (telegram-bot-pro)
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100Execution cost. Instruction body is 338 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 168: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.
External checks
ClawHub: suspicious
This Telegram bot skill broadly does what it claims, but it automatically installs an unpinned package at runtime and can run local handler code, so users should review it before installing.
LLM: suspicious (high) · VirusTotal: · 29 May 2026