yichen-wechat-mp-batch-exporter

Batch-download WeChat Official Account articles, history lists, and read/comment metrics.

2.0k|274|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/mcncarl/yichen-skills --skill yichen-wechat-mp-batch-exporter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yichen-wechat-mp-batch-exporter
Source: https://github.com/mcncarl/yichen-skills/tree/main/yichen-wechat-mp-batch-exporter
Command: npx skills add https://github.com/mcncarl/yichen-skills --skill yichen-wechat-mp-batch-exporter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Exporting WeChat Official Account content at scale is painful: article bodies, full history lists, original-article counts, and engagement metrics like reads and comments all require different tools, logins, and careful counting. This Skill orchestrates that entire batch-export workflow while keeping credentials and WeChat UI actions strictly under user control.

Core Features & Use Cases

  • Known-URL Body Download: Batch-download pasted or file-listed mp.weixin.qq.com article URLs as Markdown, JSON, text, or HTML via the public exporter API, producing an index.csv and errors.json.
  • History Export & Count Discipline: Sync a public account's article history through wechat-article-exporter, then normalize it into publish_groups, expanded_url_items, and original_articles counts with deduplicated JSON/CSV outputs.
  • Enhanced Metrics & Comments: Capture read counts, likes, shares, comments, and replies using wxdown-service credentials, with strict manual gates for QR login, certificate trust, and proxy changes.
  • Use Case: A creator wants a full archive of a benchmark account's original articles with read counts for competitive analysis. The Skill runs a read-only doctor check, guides the user through login, exports the history, analyzes count scopes, and downloads bodies plus metrics into a structured archive.

Quick Start

Ask the agent to batch download these WeChat article URLs into Markdown files, or to export a public account's full article history with original-article counts and read metrics.

Frequently Asked Questions about yichen-wechat-mp-batch-exporter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch download WeChat Official Account articles as Markdown?

Run scripts/download_urls.py with pasted URLs or a .txt/.csv/.json URL file, choosing markdown, json, text, or html format. It calls the public exporter API and writes an articles folder plus index.csv and errors.json, with no login required for known public URLs.

How to export a WeChat public account's full article history list?

Use wechat-article-exporter with a user-owned Official Account backend login: the user scans a QR code, selects the account, searches the target account, and syncs the article list. Then run scripts/analyze_history.py to normalize and deduplicate the exported history before reporting totals.

Can I get read counts, likes, and comments for WeChat articles?

Yes, but only with fresh user-owned credentials captured through wxdown-service, which runs a local mitmproxy helper. The user must trust the certificate and open articles in WeChat desktop; metrics cannot be guaranteed when credentials expire or comments are hidden.

Why does my exported article count differ from the WeChat frontend count?

The counts measure different scopes: publish_groups counts unique msgid publish groups, expanded_url_items counts every unique article URL after expanding multi-article messages, and original_articles filters by copyright_type=1, copyright_stat=1, and is_deleted=false. Compare frontend original counts only against original_articles.

What are the limitations of automated WeChat article export?

The workflow cannot bypass logins, paywalls, deleted or private articles, or platform permission checks, and it never operates the WeChat UI. QR login, certificate trust, and proxy changes always require explicit user confirmation, and public exporter endpoints may rate-limit requests.