Skills/ClawHub/xiaohongshu-preflight-check

xiaohongshu-preflight-check@1.0.1

CAUTION

Publisher claims: "小红书发布前文本合规自查（4 组）。把「发一篇笔记之前要人工过的那些关」变成一条命令 + 一个退出码：违禁词·敏感词·限流词检测（复用离线词库）、标题与篇幅规范、AI 声明与强制标注、导流风险。纯本地、零依赖、不调用付费 API，退出码 0/1/2/3 可直接卡住发布流程。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher bonniegeng-max · joined 13 days agoInstalls 456Last detonated 2 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-06 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

No findings across 1,273 lines in 13 files.

Cost to the agent

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

What would make this Verified

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim bonniegeng-max: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim bonniegeng-maxPropose a patch to the maintainer