Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
微信公众号发布工具
v2.8.0微信公众号发布工具 - 安全版 v2.8，支持 Knowledge-Base 主题、分步流程、一键发布，优化表格和 Markdown 渲染
⭐ 0· 167·0 current·0 all-time
by九章智库@xingkongqy
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name, README and runtime files clearly implement publishing to WeChat (WX_APPID/WX_SECRET, token handling, upload/publish flows). However the registry metadata lists no required environment variables or primary credential while the code and SKILL.md require WX_APPID and WX_SECRET — this mismatch is incoherent and should be corrected or explained by the author.
Instruction Scope
SKILL.md and the bundled Python implement the expected steps (md→html, fix, cover, publish). Instructions ask users to set WX_APPID/WX_SECRET via environment or .env, to clone the GitHub repo, and offer commands to run. The runtime caches tokens to /tmp/wechat_token.json and loads a local .env file into os.environ — these behaviors are expected for a publisher but you should be aware they store credentials locally and may persist environment changes if you follow the suggested ~/.bashrc approach.
Install Mechanism
There is no formal install spec (instruction-only skill), but multiple Python source files and a package.json are included. The code depends only on requests (declared in package.json). No downloads from untrusted URLs or archive extraction were observed in the provided files; installation relies on cloning the GitHub repo or using ClawHub as documented.
Credentials
Requesting WX_APPID and WX_SECRET is proportionate to a WeChat publisher. The concern is metadata omission: the skill metadata/registry does not declare these required environment variables or a primary credential while SKILL.md and the code require them and will exit if missing. That discrepancy reduces transparency about what secrets the skill needs.
Persistence & Privilege
The skill does not request elevated platform privileges (always:false). It caches the access token to /tmp/wechat_token.json and suggests adding env vars to ~/.bashrc or .env (user action). These are normal for CLI utilities; there is no evidence the skill attempts to modify other skills or system-wide configuration.
What to consider before installing
What to consider before installing:
- The tool legitimately needs your WeChat credentials (WX_APPID and WX_SECRET). Do not paste them into public places; prefer a .env file with chmod 600 or a secrets manager. The registry metadata did not declare these env vars — treat that as a transparency issue and ask the author to fix it.
- The code caches tokens to /tmp/wechat_token.json; review that file if you run the tool and remove it if you rotate credentials.
- SKILL.md suggests adding exports to ~/.bashrc which makes credentials persistent — avoid that if you don't want long-lived secrets in your shell profile. Use a secured .env or ephemeral environment variables instead.
- Review the included Python files (wechat_mp_xk.py and others) yourself or run them in an isolated environment (container or VM) before providing real credentials. Check network endpoints used by the code (the token endpoint in the file is 'https://api.weixin.qq.com/cgi-bin/stable_token' — verify this is an expected/official endpoint for your account flow).
- If you need higher assurance, ask the publisher to update the registry metadata to list required env vars and provide a provenance link (official homepage/repository) and sign or checksum releases.Like a lobster shell, security has layers — review code before you run it.
latestvk97c412gkvmde9aeef0n3n144d84r2pz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📱 Clawdis