BC tg-bot-builder-free
面向独立开发者与小团队的Telegram机器人构建助手,覆盖Bot创建、交互菜单、消息流转、群组管理等核心场景。核心能力:通过自然语言指令生成Bot配置代码,支持Reply键盘、Inline内联按钮、Webhook接入、自动回复规则与基础群组权限管理。Use
面向独立开发者与小团队的Telegram机器人构建助手,覆盖Bot创建、交互菜单、消息流转、群组管理等核心场景。核心能力:通过自然语言指令生成Bot配置代码,支持Reply键盘、Inline内联按钮、Webhook接入、自动回复规则与基础群组权限管理。Use
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationTelegramSoftware developmentAI and agentstype 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
exfil-webhook-urlSKILL.md:119Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl -s "https://api.telegram.org/bot<TOKEN>/setWebhook?url=https://yourdomain.com/webhook"
placeholder
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Map keys must be unique at line 21, column 1: suggested_price: "19.9 CNY/per_use" tools: ["read", "write", "exec"] ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "pricing_tier" - note
frontmatter-keyunknown frontmatter key "pricing_model" - note
frontmatter-keyunknown frontmatter key "suggested_price"
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1628 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
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
- +2Single-language instructions
- +3Description length 129: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (8 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: suspicious
This looks like a Telegram bot-building helper, but its broad activation wording combined with write and command-execution permissions makes it worth reviewing before install.
LLM: suspicious (high) · 23 Jul 2026