WeChat Markdown Publisher

Problem

Publishing Markdown to a WeChat Official Account usually involves handling credentials, IP allowlists, image uploads, theme rendering, and draft vs published management. This skill turns that workflow into a scriptable CLI/API path for AI or automation instead of manual copying in the WeChat console.

How it works

• Account and credentials: configure WECHAT_APP_ID and WECHAT_APP_SECRET, preferably via environment variables; the underlying wechat-md-publisher package handles storage.
• Content publishing: accepts Markdown, applies a theme such as default, orangesun, or blackink, and can create a draft or publish directly, returning media_id or publish_id.
• Image handling: supports local images, HTTP/HTTPS URLs, and WeChat CDN images; when paired with news-to-markdown, downloading images locally helps avoid signed-URL expiry and anti-hotlinking failures.
• Article management: lists drafts and published articles, deletes content, and can attach fixed header/footer media through the Wrapper feature with version history and rollback.

Boundaries

The skill depends on official WeChat APIs, so a fixed public IP must be allowlisted in the WeChat platform. AppSecret is sensitive and should only be used in trusted environments; remote themes may send article titles and body content to third-party endpoints, so verify their trustworthiness. It does not resolve WeChat content moderation, account permission differences, or Official Account type limits, so production use still requires checking account scope and content compliance.