content-factory

Before installing or running this skill, consider the following: 1) Do not trust the package solely because the registry lists no env vars — the code and docs expect GLM_API_KEY and optionally WeChat credentials. Ask the publisher to update the registry metadata to list required env vars and explain why each is needed. 2) Inspect the included Python scripts (especially yt_dlp_*, generate_cover_photo.py, wechat_publish.py, and any file that reads /root or ~/.claude paths) to confirm what files they read and what network endpoints they contact (e.g., open.bigmodel.cn). 3) Avoid storing global or high-value credentials (platform keys, production WeChat AppSecret, or other skills' keys) in the locations the skill will read; instead use a disposable/test API key if you want to try it. 4) Run the skill in an isolated environment (container, VM, or restricted user) and audit outbound network activity before allowing it access to real secrets. 5) If you need automated publishing, consider providing only a dedicated WeChat account with limited permissions. 6) Ask the author to remove or document reads of global credential paths (Tavily/Brave paths and /root/.openclaw/workspace scripts) or to make them opt-in and configurable (skill-local .env only). If the author can (a) declare the needed env vars in registry metadata, (b) confine credential access to the skill's own .env or credential file, and (c) document all external endpoints the scripts call, the package would be materially safer. If you cannot perform these checks, treat the skill as untrusted and do not run it with real/prod credentials.