Skills/ClawHub/b2b-lead-generation-zh

b2b-lead-generation-zh@1.0.1

VERIFIED· install only

Publisher claims: "B2B线索生成工具集，聚合海关贸易情报、全球企业深度背调与LinkedIn职业人脉数据。分析HS编码市场分布/趋势/占比、剖析任一公司的贸易规模/伙伴/产品/港口、获取宏观国家级贸易概览与Top买家/供应商、开展公司深度背调（员工、股东/UBO、决策人）并绘制LinkedIn职业人脉图谱（同事、校友、履历与学历）。 Trigger: B2B线索生成, 海关贸易分析, HS编码搜索, 贸易地区分布, 进出口趋势, 公司贸易占比, 企业贸易统计, 贸易伙伴分析, 宏观贸易概览, Top买家供应商, 美国进口数据, 全球企业搜索, 公司员工名单, 股东UBO, 人物搜索, 同事校友, 工作经历学历, 学校详情, 尽职调查背调, LinkedIn找公司, LinkedIn找人, 职业人脉图谱, 高管猎头, 海外线索生成, 跨境供应商寻源" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher upkuajing · publishing for 82 daysInstalls 748Last detonated 6d ago
$clawhub install b2b-lead-generation-zh
WatchReport an issue

Coverage

Nothing executable in the bundle ran; the trace covers the install step only.
Tested
every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-08 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessscript backend runs setup only
0.0sprocessscript backend runs setup only
0.0sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsSKILL.md:70 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files本技能需要 API 密钥，存储在 `~/.upkuajing/.env`：Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:79 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files先检查 `~/.upkuajing/.env` 是否有 `UPKUAJING_API_KEY`。若没有，提示用户选择：Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:81 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files2. 用户没有：用 `auth.py --new_key` 申请（自动保存到 `~/.upkuajing/.env`）Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/auth.py:49 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# 读取现有的 .env 文件Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/auth.py:45 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# 检查是否已存在 .env 文件和 API keyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:72 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescat ~/.upkuajing/.envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:80 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files1. 用户已有：用户提供（手动写入 `~/.upkuajing/.env`）Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/common.py:90 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# 如果环境变量没有，尝试从 ~/.upkuajing/.env 读取Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/auth.py:98 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# 保存到 .env 文件Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/common.py:85 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files获取API密钥，优先从环境变量，其次从 ~/.upkuajing/.env 文件。Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/common.py:19 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesUPKUAJING_ENV_FILE = UPKUAJING_DIR / '.env'Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/common.py:63 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files从 ~/.upkuajing/.env 文件加载环境变量。Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/auth.py:105 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"message": f"API密钥申请成功，但保存到 .env 文件失败：{str(e)}。\n请手动设置环境变量 {API_KEY_ENV}。",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈2,266 tok
1 file · 84 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.