Skills/ClawHub/douyin-comments-assistant

douyin-comments-assistant@1.5.0

VERIFIED· install only

Publisher claims: "用于抖音数据分析、抖音评论详情、抖音视频详情、抖音图文详情、抖音作品数据、抖音互动指标、内容调研和抖音内容分析。支持五大能力:(1) 关键词搜索视频/图文,可按点赞数、发布时间、时长、内容类型筛选排序;(2) 实时热榜查询,获取抖音热搜词条与热度数据;(3) 单条作品详情,按视频链接或 aweme_id 获取文案、互动与作者;(4) 博主作品抓取,按主页链接或 sec_uid 获取公开作品列表;(5) 视频评论分析,按视频链接或 aweme_id 获取评论内容与互动数据。Use when: 用户需要搜抖音视频、查抖音热榜/热搜、抓取博主作品列表、分析视频评论区、做短视频选题/竞品分析/舆情监控/热点追踪/爆款挖掘/抖音运营数据分析。Do NOT use when: 平台非抖音(小红书/B站/微博→对应技能)、需登录态或私密数据、仅要文案创作不需数据查询、既无关键词也无可识别链接且目标不明(先追问)。触发词:抖音搜索、抖音热榜、抖音评论、抖音博主、抖音竞品分析、短视频选题、抖音舆情、抖音数据分析、douyin search、douyin analytics、douyin comment。" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher why20261 · publishing for 65 daysInstalls 443Last detonated 22 min ago
$clawhub install douyin-comments-assistant
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-comments-assistant 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

1.4.2 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.

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-20 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.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessbundled script run in the sandbox with no arguments
0.3sprocessbundled script run in the sandbox with no arguments
0.3sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.4sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.5sprocessbundled script run in the sandbox with no arguments
0.6sprocessexited 2: (Use `node --trace-warnings ...` to show where the warning was created)
0.6sprocess8 of 29 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.6sprocessscript backend runs setup only
0.6sprocessscript backend runs setup only
0.6sprocessno install scripts to re-run

Static findings

No findings across 4,881 lines in 53 files.

Cost to the agent

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