Run WeChat public-account content operations with WeChat Article Skills
Use WeChat Article Skills to run a confirmed, multi-step WeChat article workflow from topic planning through drafting, review, formatting, images, and publishing.
npx skills add agentskillexchange/skills --skill run-wechat-public-account-content-operations-with-wechat-article-skills
Use WeChat Article Skills when an agent or content operator needs to produce WeChat public-account articles through a repeatable workflow rather than a one-off writing prompt. The workflow installs a suite of nine skills for main orchestration, topic selection, writing, review, formatting, image generation, publishing, stickers, and asset/config management. Invoke it when the agent should import or maintain a .aws configuration package, use account positioning and writing rules, draft an article, run review checks, format Markdown into WeChat-ready HTML, generate cover or inline image assets, and hand off or publish with user confirmation at each step. The scope boundary is WeChat public-account operations for agent runtimes; it is not a generic writing assistant, social-media product card, SDK, or WeChat API listing.
What this skill actually does
Inputs and prerequisites: WeChat Article Skills repository, a supported agent runtime such as OpenClaw, Claude Code, Cursor, Codex, or a Claw-compatible client, optional aiworkskills.cn configuration package, optional writing and image model API keys, and WeChat publishing credentials when publishing directly..
Setup notes: Clone https://github.com/aiworkskills/wechat-article-skills.git, then expose the skills/ directories to the target agent runtime. For OpenClaw-compatible clients, ask the agent to install the GitHub skill repository or use the documented clawhub install commands for the nine aws-wechat skills. Optionally export or import a .aws configuration package from aiworkskills.cn before starting an article workflow.
Source and verification boundary: use https://github.com/aiworkskills/wechat-article-skills#readme as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.