BC telegram-chat-tool-free
电报聊天工具免费版,为个人用户提供 Telegram Bot 创建、配置与跨实例聊天能力,支持用户艾特、消息收发与基础群组管理。核心能力: - Telegram Bot 快速创建与配置 - 跨 Bot 实例消息通信 - 用户艾特(@提及)功能 - 群组消息收发 - 基础身份标识与消息溯源 适用场景: - 个人用户搭建专属 Telegram Bot - 小团队跨 Bot 协作聊天 - 群组内艾特提醒与消息通知 差异化:免费版聚焦个人用户与小团队的 Telegram 聊天需求,提供从零开始的 Bot 配置指南...
电报聊天工具免费版,为个人用户提供 Telegram Bot 创建、配置与跨实例聊天能力,支持用户艾特、消息收发与基础群组管理。核心能力: - Telegram Bot 快速创建与配置 - 跨 Bot 实例消息通信 - 用户艾特(@提及)功能 - 群组消息收发 - 基础身份标识与消息溯源 适用场景: -…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-webhook-urlSKILL.md:251Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)curl "https://api.telegram.org/bot配置值/getUpdates" | python3 -m json.tool
vendor-hostquoted -
low Exfiltration
exfil-webhook-urlSKILL.md:365Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)curl "https://api.telegram.org/bot配置值/getUpdates"
vendor-hostquoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 258 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - 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"
Process rating: all ten parameters 53/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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 59 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1876 tokens
- 100Running it twice. No mutating operations
- low 15 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 258: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 59 items
- +4Has examples (19 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.