Skills/ClawHub/wechat-viral-topic

wechat-viral-topic@2.1.4

VERIFIED· install only

Publisher claims: "A topic-selection assistant for WeChat public accounts, short-video creators, comic authors and H5 planners that turns a raw trend into a defensible topic card. It extracts verifiable signals from source material (figures, time windows, platform fit, hashtags, conflict lines, reader pain points), screens drafts against compliance red lines (medical claims, absolute wording, income promises, incentivised sharing, unsourced assertions), and grades headlines for length, formula type and red-line risk. Ships a zero-dependency, offline, standard-library toolchain (scan / riskcheck / titlecheck) plus an 11-case golden set with a re-executable runner and a demo that proves both the block path and the no-false-positive path. Progressive disclosure: frameworks and checklists live in references/. Triggers: topic selection, viral topic, hot take, headline, WeChat article, 100k+ read. Use when choosing a WeChat public-account or short-video topic, checking a title before publishing, or screening a draft for compliance risk." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher zhaoxinghua09-cell · publishing for 85 daysInstalls 581Last detonated 29 min ago
$clawhub install wechat-viral-topic
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
2 of 2 bundled scripts run with no arguments, 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 2.1.2

vet-skills diff wechat-viral-topic 2.1.2 2.1.4

In the sandbox, this version reached for nothing 2.1.2 did not. Compared from the two recorded runs, not from source.

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-18 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 · 0 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.1sprocessexited 2: topicguard.py: error: the following arguments are required: cmd
0.1sprocess2 of 2 bundled scripts run with no arguments
0.1sprocessscript backend runs setup only
0.1sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

No findings across 1,985 lines in 26 files.

Cost to the agent

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

wechat-viral-topic@2.1.4 safety verdict: Verified (install only) — KillerSkills