BC steel-source-query
钢材货源查询与交易平台 Skill。 支持钢材现货价格查询、库存共享发布、采购需求发布、语音录入等功能的 B2B 交易平台。 触发场景: - 询问价格:"查一下螺纹钢价格"、"唐山热轧板卷多少钱"、"今天钢材行情" - 查询库存:"看看库存"、"有哪些钢材"、"查库存" - 发布库存:"我有角钢50吨"、"发布库存" - 采购需求:"我要买50吨角钢"、"发布采购需求" - 导入库存:"导入库存Excel"、"上传库存文件"、"批量导入" - 走势分析:"螺纹钢最近走势如何"、"分析一下价格"、"行情预测" - 数据源:"查看数据源状态"、"切换数据源" - 推送设置:"设置每日推送"、"取消价格推送"
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.
- 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-tokenreferences/config.template.json:33High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"to": "o9…@….wechat"
quoted -
low Dangerous commands
cmd-cron-mentionSKILL.md:390Mentions editing / listing crontabcrontab -e
Files scanned: 19. 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") - note
frontmatter-keyunknown frontmatter key "triggers"
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. No external tools needed
- 100Steps. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2011 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -33 of 15 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 13 example trigger phrases
- +3Description length 307: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (26 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.