Skills/ClawHub/douyin-creator-screening

douyin-creator-screening@1.5.0

VERIFIED· install only

Publisher claims: "输入市场、产品、合作目标等,通过关键词、品牌目标或内容方向发现、筛选和复核适合合作的抖音达人,深入分析候选账号的内容特点、真实互动数据等,评估内容能力、受众匹配与商业成本,输出有数据依据的合作候选名单。支持四大能力:(1) 关键词搜索视频/图文,可按点赞数、发布时间、视频时长、内容类型筛选排序;(2) 实时热榜查询,获取抖音热搜词条与热度数据;(3) 博主作品抓取,按主页链接或 sec_uid 获取公开作品列表;(4) 视频评论分析,按视频链接或 aweme_id 获取评论内容与互动数据。" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher why20261 · publishing for 67 daysInstalls 379Last detonated 27 min ago
$clawhub install douyin-creator-screening
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
8 of 29 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What changed since 1.4.2

vet-skills diff douyin-creator-screening 1.4.2 1.5.0

This version reaches for something 1.4.2 did not: 2 new hosts (douyin.com, guaikei.com) · 1 new credential variable (GUAIKEI_API_TOKEN). Compared from the two recorded runs, not from source.

New hosts
douyin.com, guaikei.com
New credential variables
GUAIKEI_API_TOKEN

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-22 and scored it 93/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 · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessbundled script run in the sandbox with no arguments
0.2sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.3sprocessbundled script run in the sandbox with no arguments
0.4sprocessbundled script run in the sandbox with no arguments
0.5sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.6sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.7sprocessbundled script run in the sandbox with no arguments
0.8sprocessexited 2: (Use `node --trace-warnings ...` to show where the warning was created)
0.8sprocess8 of 29 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.8sprocessscript backend runs setup only
0.8sprocessscript backend runs setup only
0.8sprocessno install scripts to re-run

Static findings

No findings across 4,953 lines in 54 files.

Cost to the agent

Instructions loaded
≈2,286 tok
1 file · 54 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.