Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Wechat Allauto Gzh

v3.0.0

微信公众号全自动写作系统。支持 20 种精美主题,自动生成封面,一键推送草稿箱。 适用场景: - 用户需要生成公众号文章草稿 - 用户想要切换多种排版主题 - 用户需要自动化内容生产流程 - 用户想要批量生成主题演示文章 <example>用户: "帮我写一篇关于人工智能的公众号文章"</example> <ex...

0· 68·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill claims a WeChat auto-writing/publishing purpose and includes push_draft.py and related code — that fits. However the registry metadata declares no required env vars or credentials while SKILL.md and multiple scripts explicitly require WECHAT_APP_ID and WECHAT_APP_SECRET (and optional TAVILY_API_KEY). That mismatch (no declared creds but runtime docs require them) is incoherent and should be corrected/clarified.
!
Instruction Scope
SKILL.md tells the agent to ask users and then run a full pipeline including reading environment variables, detecting scheduled tasks (cron/systemd), writing files, generating covers, performing web searches (Tavily) and pushing drafts to WeChat APIs. The cron_detector logic (inspecting crontab, systemd timers, config files) and instructions referencing local file paths/scripts mean the skill will inspect system state beyond just calling WeChat APIs — this expands scope and privacy impact.
Install Mechanism
There is no install spec (no packaged install), so code is included as Python scripts and a requirements.txt. That reduces supply-chain risk from remote downloads but means the agent or operator may run local Python scripts directly. No external binary downloads were declared, but included scripts like upload_to_github.py and cleanup.py can modify files and call network APIs — inspect those before running.
!
Credentials
Although the registry lists no required env vars, SKILL.md documents required WECHAT_APP_ID and WECHAT_APP_SECRET (and optional TAVILY_API_KEY and WECHAT_AUTO_MODE). Requesting WeChat credentials is expected for pushing drafts, but the absent declaration is a red flag. The skill also checks environment (WECHAT_AUTO_MODE) and system scheduling — reading these is plausible for 'auto' mode but expands access to sensitive system/state data. Ensure only minimal, test credentials are provided.
Persistence & Privilege
always:false (no forced persistence). The skill contains scripts that write to output/, cleanup or delete draft files, detect cron/systemd, and an upload_to_github.py. None of these require an always:true flag, but they do give the skill filesystem and network effects when executed. That is expected for a publish-orchestrator but increases blast radius if misused.
What to consider before installing
What to check before installing or enabling this skill: - Clarify credentials: the registry declares no required env vars but SKILL.md requires WECHAT_APP_ID and WECHAT_APP_SECRET (and optionally TAVILY_API_KEY). Do not provide production WeChat AppSecret — use a disposable/test account with minimal privileges. - Inspect network-capable scripts: review scripts/push_draft.py, scripts/update_draft.py, upload_to_github.py and any file that performs HTTP requests for unexpected endpoints or hardcoded tokens. Look for any POSTs not aimed at official WeChat endpoints. - Review local/system probing: cron_detector.py and the SKILL instructions instruct checking crontab, systemd timers, and environment variables. Decide whether you are comfortable with the skill reading system scheduling and config; run in a sandbox first. - Examine cleanup and upload helpers: cleanup.py deletes local draft/cache paths; upload_to_github.py can push to remote repos — ensure these are safe and you understand where they point. - Run in a restricted environment first: run the repository in an isolated container or VM, inspect network traffic, and only then give credentials. If possible, rotate/revoke test credentials after use. - Prefer manual approval: since the skill can autonomously perform push operations and file I/O, avoid enabling autonomous runs until you confirm the code and configuration. If you want, I can list the exact places in the code where network calls, crontab/systemd checks, or credential reads occur (e.g., lines in push_draft.py, cron_detector.py) so you can review them in detail.

Like a lobster shell, security has layers — review code before you run it.

latestvk9702j9rgjxmkmg825sq56n8pn83eg3h

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments