wechat-article-publisher

WeChat Article Publisher

Publish Markdown or HTML content to WeChat Official Account drafts via API, with automatic format conversion.

Prerequisites

WECHAT_API_KEY environment variable set (from .env file)
Python 3.9+
Authorized WeChat Official Account on wx.limyai.com

Scripts

Located in ~/.claude/skills/wechat-article-publisher/scripts/:

wechat_api.py

WeChat API client for listing accounts and publishing articles:

# List authorized accounts
python wechat_api.py list-accounts
 
# Publish from markdown file
python wechat_api.py publish --appid <wechat_appi

parse_markdown.py

Parse Markdown and extract structured data (optional, for advanced use):

Workflow

Strategy: "API-First Publishing"

Unlike browser-based publishing, this skill uses direct API calls for reliable, fast publishing.

Load WECHAT_API_KEY from environment
List available WeChat accounts (if user hasn't specified)
Detect file format (Markdown or HTML) and parse accordingly
Call publish API to create draft in WeChat
Report success with draft details

Supported File Formats:

.md files → Parsed as Markdown, converted by WeChat API
.html files → Sent as HTML, formatting preserved

Step-by-Step Guide

Step 1: Check API Key

Before any operation, verify the API key is available:

If not set, remind user to:

Copy .env.example to .env
Set their WECHAT_API_KEY value

Step 2: List Available Accounts

Get the list of authorized WeChat accounts:

Output example:

Important:

If only one account, use it automatically
If multiple accounts, ask user to choose
Note the wechatAppid for publishing

Step 3: Publish Article

For Markdown files:

For HTML files (preserves formatting):

For 小绿书 (image-text mode):

Success response:

Step 4: Report Result

After successful publishing:

Confirm the draft was created
Remind user to review and publish manually in WeChat admin panel
Provide any relevant IDs for reference

API Reference

Authentication

All API requests require the X-API-Key header:

Get Accounts List

Publish Article

Parameters:

Parameter	Type	Required	Description
wechatAppid	string	Yes	WeChat AppID
title	string	Yes	Article title (max 64 chars)
content	string	Yes	Article content (Markdown/HTML)
summary	string	No	Article summary (max 120 chars)
coverImage	string	No	Cover image URL
author	string	No	Author name
contentFormat	string	No	'markdown' (default) or 'html'
articleType	string	No	'news' (default) or 'newspic'

Error Codes

Code	Description
API_KEY_MISSING	API key not provided
API_KEY_INVALID	API key invalid
ACCOUNT_NOT_FOUND	Account not found or unauthorized
ACCOUNT_TOKEN_EXPIRED	Account authorization expired
INVALID_PARAMETER	Invalid parameter
WECHAT_API_ERROR	WeChat API call failed
INTERNAL_ERROR	Server error

Critical Rules

NEVER auto-publish - Only save to drafts, user publishes manually
Check API key first - Fail fast if not configured
List accounts first - User may have multiple accounts
Handle errors gracefully - Show clear error messages
Preserve original content - Don't modify user's markdown unnecessarily

Supported Formats

Markdown Files (.md)

H1 header (# ) → Article title
H2/H3 headers (##, ###) → Section headers
Bold (text)
Italic (text)
Links text
Blockquotes (> )
Code blocks (...)
Lists (- or 1.)
Images → Auto-uploaded to WeChat

HTML Files (.html)

<title> or <h1> → Article title
All HTML formatting preserved (styles, tables, etc.)
<img> tags → Images auto-uploaded to WeChat
First <p> → Auto-extracted as summary
Supports inline styles and rich formatting

HTML Title Extraction Priority:

<title> tag content
First <h1> tag content
"Untitled" as fallback

HTML Content Extraction:

If <body> exists, uses body content
Otherwise, strips <html>, <head>, <!DOCTYPE> and uses remaining content

Article Types

news (普通文章)

Standard WeChat article format
Full Markdown/HTML support
Rich text with images

newspic (小绿书/图文消息)

Image-focused format (like Instagram posts)
Maximum 20 images extracted from content
Text content limited to 1000 characters
Images auto-uploaded to WeChat

Example Flow

Markdown File

User: "把 ~/articles/ai-tools.md 发布到微信公众号"

HTML File

User: "把这个HTML文章发布到公众号：~/articles/newsletter.html"

Error Handling

API Key Not Found

Solution: Ask user to set up .env file with their API key.

Account Not Found

Solution: Ask user to authorize their account on wx.limyai.com.

Token Expired

Solution: Ask user to re-authorize on wx.limyai.com.

WeChat API Error

Solution: May be temporary issue, retry or check WeChat service status.

Best Practices

Why use API instead of browser automation?

Reliability: Direct API calls are more stable than browser automation
Speed: No browser startup, page loading, or UI interactions
Simplicity: Single command to publish
Portability: Works on any system with Python (no macOS-only dependencies)

Content Guidelines

Images: Use public URLs when possible; local images will be uploaded
Title: Keep under 64 characters
Summary: Auto-extracted from first paragraph if not provided
Cover: First image in markdown becomes cover if not specified

Workflow Efficiency

Troubleshooting

Q: How do I get a WECHAT_API_KEY?

A: Register and authorize your WeChat account at wx.limyai.com to get your API key.

Q: Can I publish to multiple accounts?

A: Yes, use list-accounts to see all authorized accounts, then specify the target --appid.

Q: Images not showing in WeChat?

A: Ensure images are accessible URLs. Local images are auto-uploaded but may fail if path is incorrect.

Q: Title is too long?

A: WeChat limits titles to 64 characters. The script will use the first 64 chars of H1.

Q: What's the difference between news and newspic?

A: news is standard article format; newspic (小绿书) is image-focused with limited text.

新手上路（用户不知道该输入什么时，走这里）

触发：/公众号发布新手、「这个怎么用」「第一次用」「能干嘛」「带我走一遍」，以及用户输入了技能名却没有给任何任务的时候。

这个模式的铁律：不假设、不索取。用户可能什么都没准备，不要一上来就问他要文件、要 API key、要具体需求。按下面四步走：

一、先说清楚这是什么（三句话以内）

一句话：把 Markdown 文章直接发进公众号草稿箱，图片自动上传。走的是微信官方接口，不是模拟点击，所以稳定。发的是草稿，最终点「发表」的还是你。

二、给编号选项，让他按回车就能继续

不要问开放式问题（「你想做什么？」对新手是负担）。给 3 个选项加一个默认：

三、直接演示一遍，边做边解释

选完立刻做给他看，用示例数据，不需要他提供任何东西。每做完一步，加一行「💡 刚才发生了什么」，一句话说明这步的意义。

四、毕业

演示完只问一个是非题：「要不要用你自己的文章真跑一遍？」答是就进正常流程；答否就告诉他随时回来输 /公众号发布新手。

关于前置条件：这个技能需要公众号的 API 凭据（写在 .env 里的 WECHAT_API_KEY）。新手模式下不要提前索取——先用示例数据演示完，到第四步真跑的时候再引导他配置，并说清楚在哪配、怎么拿。新手最容易在这一步流失。