BF ai-sales-lead-radar
AI销售线索雷达。当政企销售/BD/渠道人员想找销售线索、开发客户时，必须使用此SKILL：销售线索挖掘、潜在客户发现、拟建项目（提前6-18个月布局）、采购意向（发标前1-3个月对接）、临期续约（替换现供应商）、线索按金额与紧急度排序、每日商机晨报订阅。给一个行业/产品/地区即输出按价值排序的线索清单。即使用户没有提到「线索」，只要涉及找客户、开发市场、挖商机、谁会买我们产品等需求，都应使用本SKILL。
AI销售线索雷达。当政企销售/BD/渠道人员想找销售线索、开发客户时，必须使用此SKILL：销售线索挖掘、潜在客户发现、拟建项目（提前6-18个月布局）、采购意向（发标前1-3个月对接）、临期续约（替换现供应商）、线索按金额与紧急度排序、每日商机晨报订阅。给一个行业/产品/地区即输出按价值排序的线索清单。即使用户没有…
As a process F 35/100 · Will not run — References files that are not bundled: references/auto-register.md, references/workflow.md, references/api-quick.md
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: 0. 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: references/auto-register.md - warning
missing-refreference to a missing file: references/workflow.md - warning
missing-refreference to a missing file: references/api-quick.md - warning
missing-refreference to a missing file: references/report-template.md - warning
missing-refreference to a missing file: scripts/render_report.py
Process rating: all ten parameters 35/100
- 0Tools and files. 5 referenced file(s) missing: references/auto-register.md, references/workflow.md, references/api-quick.md
- 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. 35 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1748 tokens
- 100Running it twice. No mutating operations
- low 11 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
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 205: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.