BF b2b-lead-generation-zh
B2B线索生成工具集,聚合海关贸易情报、全球企业深度背调与LinkedIn职业人脉数据。分析HS编码市场分布/趋势/占比、剖析任一公司的贸易规模/伙伴/产品/港口、获取宏观国家级贸易概览与Top买家/供应商、开展公司深度背调(员工、股东/UBO、决策人)并绘制LinkedIn职业人脉图谱(同事、校友、履历与学历)。 Trigger: B2B线索生成, 海关贸易分析, HS编码搜索, 贸易地区分布, 进出口趋势, 公司贸易占比, 企业贸易统计, 贸易伙伴分析, 宏观贸易概览, Top买家供应商, 美国进口数据, 全球企业搜索, 公司员工名单, 股东UBO, 人物搜索, 同事校友, 工作经历学历, 学校详情, 尽职调查背调, LinkedIn找公司, LinkedIn找人, 职业人脉图谱, 高管猎头, 海外线索生成, 跨境供应商寻源
B2B线索生成工具集,聚合海关贸易情报、全球企业深度背调与LinkedIn职业人脉数据。分析HS编码市场分布/趋势/占比、剖析任一公司的贸易规模/伙伴/产品/港口、获取宏观国家级贸易概览与Top买家/供应商、开展公司深度背调(员工、股东/UBO、决策人)并绘制LinkedIn职业人脉图谱(同事、校友、履历与学历)。…
As a process F 35/100 · Will not run — References files that are not bundled: indexes/customs-analysis.md, indexes/customs-company.md, indexes/customs-overview.md
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
read-dotenvSKILL.md:72Reads a .env filecat ~/.upkuajing/.env
Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: indexes/customs-analysis.md - warning
missing-refreference to a missing file: indexes/customs-company.md - warning
missing-refreference to a missing file: indexes/customs-overview.md - warning
missing-refreference to a missing file: indexes/global-depth.md - warning
missing-refreference to a missing file: indexes/linkedin.md - warning
missing-refreference to a missing file: scripts/*.py - warning
missing-refreference to a missing file: references/<xxx>-api.md
Process rating: all ten parameters 35/100
- 0Tools and files. 7 referenced file(s) missing: indexes/customs-analysis.md, indexes/customs-company.md, indexes/customs-overview.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. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2113 tokens
- 100Running it twice. No mutating operations
- 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)
- +3Output format is not stated: the model decides each time
- -336 of 39 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 370: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (39 of 39)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.