Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Mp Publisher
v1.0.1Automates WeChat article workflow: generates topics, drafts, reviews, creates images, and publishes drafts to the official account.
⭐ 0· 28·0 current·0 all-time
by吴曦@wuxixixi
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 and description (WeChat article workflow + publishing drafts) match the implemented functionality: lib/draft_publisher.py interacts with the WeChat API, lib/image_generator.py calls a DMX image API, SKILL.md documents WECHAT_APP_ID/WECHAT_APP_SECRET and DMX_API_KEY. However, the registry metadata declares no required env vars or primary credential while the code and SKILL.md clearly require two secrets; this mismatch is surprising and should be resolved before trusting the skill.
Instruction Scope
SKILL.md stays on-topic: it documents the workflow, file locations under ~/.openclaw, required env files, IP whitelist for WeChat, and that it only creates drafts. The runtime instructions and role mapping align with the code behavior (parsing article files, generating images, uploading to WeChat). There are no instructions to read unrelated system files or exfiltrate data to unexpected endpoints.
Install Mechanism
There is no formal install spec in the registry, but package includes scripts/setup.sh which copies files into ~/.openclaw/workspace-*, creates .env templates, and invokes pip to install requests and wechatpy. This is a reasonable local install approach, but the skill will write to the user's home and install Python packages—users should review the script before running it.
Credentials
The code legitimately requires WECHAT_APP_ID and WECHAT_APP_SECRET (used to fetch access_token and create drafts) and DMX_API_KEY (used to generate images). These are proportionate to the declared purpose. The concern is that the registry metadata did not list these required env vars (package.json does list them under config.env, but the registry summary shows none), which is an inconsistency that could lead users to miss supplying or auditing sensitive keys.
Persistence & Privilege
The skill does not request always:true and is user-invocable. setup.sh writes files into ~/.openclaw workspace subdirectories and installs helper scripts there; this is scoped to its own workspace and does not modify other skills or global agent settings. No evidence of elevated or hidden persistence beyond installing its own tools.
What to consider before installing
What to consider before installing:
- The skill requires two secrets (WECHAT_APP_ID & WECHAT_APP_SECRET) and a DMX API key — those are necessary for its claimed WeChat publishing and image-generation functionality. Do not provide those credentials unless you trust the code and the DMX provider.
- The registry metadata did not declare required env vars, but the SKILL.md and code do; this discrepancy is a red flag about packaging hygiene. Inspect SKILL.md, package.json, and the code yourself (they are included) before running any setup script.
- setup.sh will create directories and .env templates under ~/.openclaw and copy Python scripts there; it also attempts to pip-install packages (requests, wechatpy). Run the script in a controlled environment (or review/edit it) rather than executing blindly.
- Verify the DMX_BASE_URL and DMX provider (default https://www.dmxapi.cn) are intended; if you prefer a different image service, change the code or envs.
- Recommended precautions: review the Python files (draft_publisher.py, image_generator.py, workflow-monitor.py) to ensure no secrets are being logged or sent to unexpected endpoints; run first in a sandbox or VM; supply least-privileged credentials; add the host IP to WeChat whitelist only after validating behavior.
Why 'suspicious' not 'malicious': The code implements exactly what the skill advertises and uses appropriate APIs, but the packaging/metadata inconsistency and the fact that setup writes to the home directory and installs packages without a registry-declared install spec are concerning enough to require human review before use. Additional information that would raise confidence: amended registry metadata listing required env vars, a trusted upstream repository URL and release artifacts, or a signed/verified package release.Like a lobster shell, security has layers — review code before you run it.
latestvk971wcrpzsty6tbyjr5t8g0b89847wd8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
