Skills/ClawHub/wechat-file-organizer

wechat-file-organizer@2.3.0

VERIFIED· install only

Publisher claims: "微信文件自动归类(无头版)——扫描微信接收文件目录,按类型/月份归类、去重、生成报告;支持 JSON 规则自定义归类(按文件名/路径/扩展名)与单文件 HTML 可视化报告(内嵌 CSS+SVG,无外部依赖)。零依赖、默认只读(dry-run);清理源文件优先移入系统回收站/废纸篓,不提供永久删除选项。扫描逻辑与 GUI 应用 wechat-file-organizer-gui(main.py)同步。" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher oracis · publishing for 64 daysInstalls 741Last detonated 28 min ago
$clawhub install wechat-file-organizer
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.2.0

vet-skills diff wechat-file-organizer 2.2.0 2.3.0

In the sandbox, this version reached for nothing 2.2.0 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-22 and scored it 92/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.2sprocessexited 2:
0.2sprocess2 of 2 bundled scripts run with no arguments
0.2sprocessscript backend runs setup only
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedscripts/organize.py:463 · Python subprocess execution detectedr = subprocess.run(["osascript", "-e", script],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 2,148 lines in 7 files.

Cost to the agent

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