BF news-aggregator
国内外社会、科技、军事新闻聚合引擎，自动搜索、筛选、整理新闻要点。覆盖国内科技、 国内军事、国际科技、国际军事四大板块。核心能力： - 多源新闻搜索（国内科技/军事+国际科技/军事） - 自动去重与可信度过滤 - 结构化汇总（标题+来源+时间+要点） - 按类别分类整理 - 可信度评级（官方媒体优先、匿名消息谨慎）。可自动提升工作效率 功能涵盖: aggregator。
As a process F 35/100 · Will not run — References files that are not bundled: 链接
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.
- The text references files that are not there: add them or drop the references.
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: 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: Nested mappings are not allowed in compact mappings at line 8, column 14: description: 国内外社会、科技、军事新闻聚合引擎，自动搜索、筛选、整理新闻要点。覆盖国内科技、 国内军事、国际科技、国际军事四大板块。核心能力： … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 186 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 - warning
missing-refreference to a missing file: 链接 - 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 "tools" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 35/100
Will not run. References files that are not bundled: 链接
- 0Tools and files. 1 referenced file(s) missing: 链接
- 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. 71 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1836 tokens
- 100Running it twice. No mutating operations
- low 19 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 186: enough signal without eating the budget
- +4Structure: 48 headings
- +3Step-by-step instructions: 71 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 48.
External checks
ClawHub: suspicious
This news aggregation skill has no executable payload, but it asks for broad read/exec capability and includes an under-explained callback URL that could send results outside the agent.
LLM: suspicious (medium) · 14 Aug 2026