WeChat Official Account Content Generation and Publishing

Problem Addressed

When managing a WeChat Official Account, publishing content from Markdown drafts involves manual steps such as coding, generating images, uploading them, and pushing drafts. This process is time-consuming and prone to errors like formatting issues or image handling failures, especially for technical blogs where code highlighting and structured imagery add complexity.

Core Capabilities and Workflow

The skill automates key aspects of WeChat content publishing, with core capabilities:

• Smart Image Generation: Analyzes article structure to automatically generate 1-4 16:9 aspect ratio images based on section count, with 4px rounded corners added. Uses the generate_images.py script, integrated with JimengAI for image creation, ensuring images are uploaded to WeChat CDN.
• One-Click Publishing: Via the wenyan publish command, it renders Markdown into WeChat-compatible format, uploads all body images to WeChat CDN, and pushes the result to drafts without manual intervention.
• Theme Support: Includes visual themes like lapis, phycat, and default, along with code highlighting themes such as solarized-light and monokai for consistent styling.

The workflow is streamlined into three steps:
1. Prepare the Markdown file with frontmatter at the top including required fields like title and cover.
2. Run the setup.sh script to load WeChat Official Account and JimengAI credentials into environment variables.
3. Execute the publish command, which handles image generation, uploading, and draft pushing automatically.

Applicability and Limitations

The skill depends on the wenyan-cli command-line tool, which must be installed first. Configuration requires obtaining WeChat AppID and AppSecret (from the WeChat Official Account platform settings), and JimengAI access keys (from the Volcengine console), along with adding the server's public IP to the WeChat IP whitelist. Common issues include IP whitelist errors (error code 45166), invalid credentials, or image generation bugs (such as historical issues with blank images), necessitating checks on the config.env file and script versions. It is suited for structured technical content publishing, but custom image styling may be limited by built-in rules, and publishing delays can cause draft updates to not appear immediately.