Skills/ClawHub/zsxq-post-fetch

zsxq-post-fetch@1.2.0

VERIFIED· install only

Publisher claims: "知识星球帖子抓取助手 — 默认通过官方 zsxq-cli OAuth/Keychain 登录态抓取用户已授权账号可访问的帖子,支持全部/精华筛选、关键词搜索、单帖详情、日期范围导出、多星球配置、Markdown 和附件整理。本 Skill 应在用户需要查看、汇总、检索或导出知识星球内容时使用。" Observed in sandbox: reads credential files.

Registry ClawHubPublisher wufulin · publishing for 153 daysInstalls 704Last detonated 28 h ago
$clawhub install zsxq-post-fetch
WatchReport an issue

Coverage

Install scripts ran; no agent task scenario for this bundle.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 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 (2 scenarios; install scripts ran; no agent task scenario for this bundle) on 2026-11-13 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: reads credential files.

Behavior trace

Honeypot run · 4 s · 2 scenarios
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
1.7sfilesystemread ~/.npmrc
1.7sfilesystemread ~/.npm/_logs · ~/.npm/_cacache/index-v5/82/1b/28661384bdcaa741f4f07e6f6992b290b6dc330db6accbf83a5983336286 · ~/.npm/_cacache/index-v5/b2/ed/07cd8ac1e715a3d35a3f57d7aad3242df68fb6408651fb1c86f314c3523f · ~/.npm/_cacache/index-v5/bf/fa/dfa1a544bff4ff397507bb1533a50e7d38bbd135780be93ed80a0503f3e0 · ~/.npm/_cacache/index-v5/c4/f1/b02a898d17e383063af4290add4168c4c8fa7500b6fee270563f708c93a3 · ~/.npm/_cacache/index-v5/c2/18/564dd4be228cbfeb671dc4bef72b65ab4e3781387797358ec4bedb0fdc61 outside project
1.7sfilesystemwrote ~/.npm/_cacache/tmp/b1bed581 · ~/.npm/_cacache/index-v5/82/1b/28661384bdcaa741f4f07e6f6992b290b6dc330db6accbf83a5983336286 · ~/.npm/_cacache/tmp/130cda05 · ~/.npm/_cacache/index-v5/b2/ed/07cd8ac1e715a3d35a3f57d7aad3242df68fb6408651fb1c86f314c3523f · ~/.npm/_cacache/tmp/4a7045d1 · ~/.npm/_cacache/index-v5/c2/18/564dd4be228cbfeb671dc4bef72b65ab4e3781387797358ec4bedb0fdc61
1.7snetworkCONNECT tcp://registry.npmjs.org:443
1.7snetworkCONNECT tcp://registry.npmjs.org:443
1.7snetworkCONNECT tcp://registry.npmjs.org:443
1.7snetworkCONNECT tcp://registry.npmjs.org:443
1.7snetworkCONNECT tcp://registry.npmjs.org:443
1.7snetworkCONNECT tcp://registry.npmjs.org:443
1.7sprocessexec /usr/bin/dirname
1.7sprocessexec /usr/bin/sed
1.7sprocessexec /usr/bin/cut
1.7sprocessexec /usr/local/bin/npm
1.7sprocessexited 1: npm error A complete log of this run can be found in: /tmp/ks-detonate-J7qDjT/setup/home/.npm/_logs/2026-11-13T10_29_49_375Z-debug-0.log
1.7sprocessscript backend runs setup only
1.7sprocessscript backend runs setup only
2.2sprocesssecond launch, clock +45 days, CI unset
3.6sfilesystemread ~/.npmrc
3.6sfilesystemread ~/.npm/_logs · ~/.npm/_cacache/index-v5/82/1b/28661384bdcaa741f4f07e6f6992b290b6dc330db6accbf83a5983336286 · ~/.npm/_cacache/content-v2/sha512/93/f5/3d20df0577429335d07be54ba9a9f4de53ac809a0e760f7532cdbd3fd9567f568a9d7e21b19ca8c98a0edab30738d663a40dccb2afce7b894d836205c932 · ~/.npm/_cacache/index-v5/b2/ed/07cd8ac1e715a3d35a3f57d7aad3242df68fb6408651fb1c86f314c3523f · ~/.npm/_cacache/index-v5/bf/fa/dfa1a544bff4ff397507bb1533a50e7d38bbd135780be93ed80a0503f3e0 · ~/.npm/_cacache/index-v5/c4/f1/b02a898d17e383063af4290add4168c4c8fa7500b6fee270563f708c93a3 outside project
3.6sfilesystemwrote ~/.npm/_cacache/tmp/d3654c9a · ~/.npm/_cacache/index-v5/82/1b/28661384bdcaa741f4f07e6f6992b290b6dc330db6accbf83a5983336286 · ~/.npm/_cacache/tmp/682a328b · ~/.npm/_cacache/tmp/9aca70ee · ~/.npm/_cacache/tmp/85a3c67d · ~/.npm/_cacache/tmp/176fdf59
3.6snetworkCONNECT tcp://registry.npmjs.org:443
3.6snetworkCONNECT tcp://registry.npmjs.org:443
3.6snetworkCONNECT tcp://registry.npmjs.org:443
3.6snetworkCONNECT tcp://registry.npmjs.org:443
3.6snetworkCONNECT tcp://registry.npmjs.org:443
3.6snetworkCONNECT tcp://registry.npmjs.org:443
3.6sprocessexec /usr/bin/dirname
3.6sprocessexec /usr/bin/sed
3.6sprocessexec /usr/bin/cut
3.6sprocessexec /usr/local/bin/npm
3.6sprocessexited 1: npm error A complete log of this run can be found in: /tmp/ks-detonate-J7qDjT/later/home/.npm/_logs/2026-12-28T10_29_51_541Z-debug-0.log

Static findings

No findings across 3,394 lines in 12 files.

Cost to the agent

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