BF telegram-alert
面向专业交易团队的多通道告警通知系统。支持Telegram多群组推送、 复合触发条件、富媒体消息（图表/图片）、定时播报与团队协作功能。 适用于需要消息发送、通知推送、通信集成的场景。不适用于垃圾信息群发。Use when 用户需要telegram-alert相关功能时使用。不适用于超出本技能能力范围的复杂需求。
面向专业交易团队的多通道告警通知系统。支持Telegram多群组推送、 复合触发条件、富媒体消息（图表/图片）、定时播报与团队协作功能。 适用于需要消息发送、通知推送、通信集成的场景。不适用于垃圾信息群发。Use when 用户需要telegram-alert相关功能时使用。不适用于超出本技能能力范围的复杂需求。
As a process F 35/100 · Will not run — References files that are not bundled: references/style.md, assets/output.json
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 157 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: references/style.md - warning
missing-refreference to a missing file: assets/output.json - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "summary_zh" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: references/style.md, assets/output.json
- 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
- 100Steps. 70 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3004 tokens
- 100Running it twice. No mutating operations
- low 24 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 157: enough signal without eating the budget
- +4Structure: 55 headings
- +3Step-by-step instructions: 70 items
- +4Has examples (8 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.