AC fore-vip-find-customers
找客户 · B2B 客户挖掘与获客助手（fore.vip）。把「帮我找客户 / 我的货卖给谁 / 客户挖掘 / 获客 / 潜在客户 / 下游客户推荐 / 销售线索」转化为可执行的客户线索清单。标准流程：① 需求采集（行业、产品、区域、客户画像）② 产业链下游分析（下游行业类型与需求点）③ 多源客户采集（行业门户、搜索引擎、社区频道、官网、大模型知识，逐条标注来源·时间）④ 结构化客户清单（公司/行业/责任人/联系方式/官网/匹配度/来源）⑤ 邮件直推（客户有公开邮箱即经 Agent Mail 推送配图，图内嵌联系方式）⑥ 线索稀缺时的补偿获客（发布渠道清单 + 合规发布范式 + ImageGen 配图 + 引导附带联系方式）。遵循合规红线：只用公开信息、不采隐私数据、发布内容不做硬广导流。当用户为产品或服务寻找买家、挖掘潜在客户、拓展销售渠道时使用。
找客户 · B2B 客户挖掘与获客助手（fore.vip）。把「帮我找客户 / 我的货卖给谁 / 客户挖掘 / 获客 / 潜在客户 / 下游客户推荐 / 销售线索」转化为可执行的客户线索清单。标准流程：① 需求采集（行业、产品、区域、客户画像）② 产业链下游分析（下游行业类型与需求点）③…
As a process C 51/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 · 0
✓ No critical or high findings
Files scanned: 3. 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 51/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
- 100Tools and files. No external tools needed
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 991 tokens
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 380: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.