Markdown WeChat Push

The Problem

WeChat article bodies do not support external CSS, so pasting raw Markdown often loses styling, breaks tables, and becomes hard to maintain when long posts hit platform limits. This skill targets technical writing workflows that need a reliable path from Markdown to WeChat-compatible HTML, with optional draft pushes to WeChat or Juejin.

How It Works

The workflow is split into three levels: md2wechat_html.py handles conversion only, push_daily.py converts and pushes to WeChat, and push_juejin.py pushes to Juejin. Conversion supports headings, body text, bold, links, inline code, code blocks, blockquotes, and tables, and inlines CSS into style attributes. Article mode includes seven preset styles that can be selected by natural language or by --config; news mode is aimed at sectioned daily reports and should be explicitly requested. Before pushing to WeChat, the flow reads title and digest from frontmatter and, when digest is missing, requires a generated Chinese summary of up to 120 characters to avoid hard truncation. Output over 20,000 characters is split by H2 headings and labeled with suffixes such as (Part 1), (Part 2), and (Part 3). The Juejin path parses frontmatter, uploads local images to the Juejin image host, replaces them with CDN URLs, and creates or updates a draft.

Boundaries And Caveats

Conversion-only use has no extra prerequisites; WeChat push requires ~/.md_push_wechat/config.yaml with appid and secret, and the flow must not auto-create or search for it. Juejin push depends on juejin.cookie, which is valid for about 30 days. Image upload is best-effort, and failed uploads leave the original reference intact. The skill does not verify facts, handle copyright, or satisfy WeChat review rules; it focuses on formatting, digest preparation, and draft delivery.