SKILLEMALL.ai

BD 热点检索输出报文

定时从白名单企业(默认 OpenAI·Google·NVIDIA·Anthropic·DeepSeek·阿里巴巴·字节跳动·Tesla·SpaceX)抓取24小时内热点,用搜索工具 content摘要直接撰写中文短文(默认400 字),发送纯文字(默认3 条、无图)到推送渠道。模型、搜索、白名单、字数、推送渠道、触发时间全部可配置,含反幻觉+敏感词回避规则。

ClawHub Agent Skills author: yuewuya20180928 v1.0.0 MIT-0 5 files body ≈ 1 766 tokens Open the sourceclawhub.ai analyzed 3 d ago

定时从白名单企业(默认 OpenAI·Google·NVIDIA·Anthropic·DeepSeek·阿里巴巴·字节跳动·Tesla·SpaceX)抓取24小时内热点,用搜索工具 content摘要直接撰写中文短文(默认400 字),发送纯文字(默认3…

As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationTelegramAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
98
Quality 40%
71
Run on models
none yet
Process rating
D
39/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Secrets in code secret-high-entropy-token references/prompt.md:42
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | `${RECIPIENT}` | `o9…@….wechat` |
    table
  • low Dangerous commands cmd-background-process SKILL.md:227
    Starts a background / autostarted process
    nohup systemctl --user stop openclaw-gateway > /dev/null 2>&1 &

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 39/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. 4 mutating operations with no state check
  • 40Consistency. Frontmatter name (热点检索输出报文) differs from the folder (redian-jiansuo-baochuwen)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 17 steps
  • 100Execution cost. Instruction body is 1766 tokens
  • low 10 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 180: enough signal without eating the budget
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (12 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.

External checks

ClawHub: suspicious
This skill does what it says, but its recurring outbound messaging and local credential/reset instructions need human review before installation.
LLM: suspicious (high) · 11 Jun 2026