BD digital-sub
查询企业名称或纯数字股票代码对应的近24小时企业舆情日报，并在缺少 kr_skills_api_key 时完成 API Key 申请、微信扫码绑定和后续查询。适用于企业全情报订阅场景；不用于创建、修改或发布企业业务数据。
查询企业名称或纯数字股票代码对应的近24小时企业舆情日报，并在缺少 krskillsapikey 时完成 API Key 申请、微信扫码绑定和后续查询。适用于企业全情报订阅场景；不用于创建、修改或发布企业业务数据。
As a process D 43/100 · Unfinished process — 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 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/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. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 100Steps. 43 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1092 tokens
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +3Description length 110: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 11 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: suspicious
The skill has a legitimate company-report purpose, but it can auto-run, store an API key persistently, and send credentials over an insecure endpoint without clear user control.
LLM: suspicious (high) · 10 Sept 2026