BF b2b-factory-search
给企业采购人（买家）用的选厂助手：把一句"谁家能做"变成一份带工商信息与能力标签的候选厂家清单， 供采购筛选生产/代工/定制合作伙伴后进店沟通。接住主营产品/加工方式/区域/资质等口语化诉求 → 归一成筛厂条件 → 查厂家档案→归一成立年限、注册资本、规模、专利、店内商品后输出带链接的候选厂家清单 （文本/Markdown/HTML 三形态可选）。只报档案里取到的信息，取不到就说取不到， 绝不编产能、编资质、编交期；只做信息呈现，不下"哪家确定靠谱/值得合作"的评级结论。 只做查询整理，不代下单、不代发询盘；联系方式不直出，由用户点击跳转查看。 触发词: 找厂家, 有没有能生产…的工厂, 想找源头厂, 谁家能代工, 这个品类的工厂都在哪,找个有资质的生产厂, 定制加工找谁, OEM/ODM 找厂
给企业采购人（买家）用的选厂助手：把一句"谁家能做"变成一份带工商信息与能力标签的候选厂家清单， 供采购筛选生产/代工/定制合作伙伴后进店沟通。接住主营产品/加工方式/区域/资质等口语化诉求 → 归一成筛厂条件 → 查厂家档案→归一成立年限、注册资本、规模、专利、店内商品后输出带链接的候选厂家清单…
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.
- 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: 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") - warning
missing-refreference to a missing file: 店铺页链接
Process rating: all ten parameters 35/100
- 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. 44 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 895 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
- +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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 352: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 44 items
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.