WeWrite

In plain terms — the skill appears to do what it says (write and publish WeChat articles), but its code and runtime steps expect credentials and access that were not declared in the skill metadata, and it will look for config files beyond the skill folder and can pull code from the network. Before installing or running this skill: - Expect to provide WeChat credentials (appid + secret) if you want publishing/stats to work, and an image API key if you want image generation. The skill does not list these as required env vars, so supply them consciously and avoid putting other secrets in the same config file. - Review toolkit/wechat_api.py, scripts/fetch_stats.py, and toolkit/image_gen.py to confirm what is sent to external endpoints and whether any identifiers are logged or transmitted. - Be cautious about the 'git pull origin main' update step: running it will fetch and run remote code. Only run updates from a trusted repository or inspect the fetched changes before executing. - The scripts search multiple config locations (including ~/.config/wewrite/config.yaml). If you have unrelated configs in your home directory, move or inspect them; sensitive credentials there could be read. - Dependencies are installed ad-hoc via pip if needed; run pip install in a virtualenv or sandbox and inspect requirements.txt first. - If you want minimal risk, run the skill in an isolated environment (container or VM), give it only the credentials it needs for the features you intend to use, and avoid granting it broad access to your home directory or long-lived LLM keys unless necessary. If you want, I can list the specific files and lines that reference external endpoints, home paths, or LLM keys so you (or an admin) can audit them before use.