WeChat Pipeline

This skill is used to orchestrate the WeChat Official Account content production process into a fixed pipeline.

The goal is to only use off-the-shelf skills to standardize the production process as:

Topic Selection -> Research -> Writing -> Optimization -> Distribution

This is the public orchestration entry in the repository.

Users should treat it as the process entry, rather than treating internal subskills as peer options.

When to use

Use it when users want to quickly build a set of official account content pipelines in Codex, or explicitly need to do the following things:

Plan WeChat Official Account content production process
Use skills to connect topic selection, research, writing, typesetting, and publishing
Mass produce official account articles
Retain replaceable structure for subsequent expansion to other channels

Allowed Skills

Main pipeline:

```
keyword-research
```
```
seo-content-brief
```
```
knowledge-article-calibrator
```
(optional, pre-writing calibration)
```
seo-content-writer
```
```
knowledge-article-auditor
```
(optional, post-writing review)
```
baoyu-format-markdown
```
```
baoyu-markdown-to-html
```
```
baoyu-post-to-wechat
```

Official account quick writing pipeline:

```
wechat-topic-outline-planner
```
```
knowledge-article-calibrator
```
(optional, pre-writing calibration)
```
wechat-article-writer
```
```
knowledge-article-auditor
```
(optional, post-writing review)
```
baoyu-format-markdown
```
```
baoyu-markdown-to-html
```
```
baoyu-post-to-wechat
```

The main pipeline is prioritized by default. Switch to the quick writing pipeline only in the following cases:

User explicitly requests to "use the official account quick writing pipeline"
The current topic emphasizes WeChat Official Account expression more than research depth
The research or writing skills in the main pipeline are obviously not suitable for the current goal

Recommended Enhanced Skills in This Repository

This pipeline allows access to public skills in this repository as enhancement nodes:

```
ai-workflow-brand
```
```
reader-hook
```

knowledge-article-system

(including

knowledge-article-calibrator

and

knowledge-article-auditor

)

Usage principles:

If the topic direction, positioning, and column attribution are still unclear, use
```
ai-workflow-brand
```
first
If the main line of the article is fine, but the title and opening are not attractive enough, use
```
reader-hook
```
If you need to check whether the content deviates from the theme before publishing, also use
```
ai-workflow-brand
```
If the article is knowledge-based judgment content (AI, workflow, cognition, content production, judgment), use
```
knowledge-article-calibrator
```
for pre-writing calibration before writing, and use
```
knowledge-article-auditor
```
for review and scoring after the first draft is completed
If you are not sure which one to use, route through the parent skill
```
knowledge-article-system
```

Do not require users to directly memorize the internal subskills of

ai-workflow-brand

. For users, the public entry is always the parent skill.

Working Directory

The working root directory uses

<workspace_root>

Default value:

/root/workspace/data/wechat-pipeline

Directory convention:

```
<workspace_root>/00_topics/
```
```
<workspace_root>/01_research/
```
```
<workspace_root>/02_drafts/
```
```
<workspace_root>/03_polish/
```
```
<workspace_root>/04_publish/
```
```
<workspace_root>/_state/
```

slug

is not required by default.

If the user does not provide

slug

, it is automatically generated according to the following rules:

YYYY-MM-DD-topic

Generation rules:

Use the current local date for the date
Use the topic text given by the user for the topic
Replace spaces with
```
-
```
Remove punctuation that is obviously not suitable for file names
Both Chinese or ASCII alphanumeric characters can be retained, no need to force conversion to Pinyin

Example:

Topic:
```
AI 工作流
```
Automatically generated:
```
2026-03-17-AI-工作流
```

Fixed file contract:

Topic selection output:
```
<workspace_root>/00_topics/<slug>.md
```
Research output:
```
<workspace_root>/01_research/<slug>.md
```
First draft output:
```
<workspace_root>/02_drafts/<slug>.md
```
Optimization output:
```
<workspace_root>/03_polish/<slug>.md
```
Publishing output:
```
<workspace_root>/04_publish/<slug>.html
```
Status file:
```
<workspace_root>/_state/<slug>.json
```

Core Rules

Only advance one stage at a time, do not skip steps.
Each stage must have clear input files and output files.
If the product of the previous step does not exist, do not proceed to the next step.
Prioritize reusing existing products unless the user explicitly requests a rewrite.
After completing each step, briefly report the current product path and the next step.
Unless the user explicitly says "publish", pause after generating the HTML product.
If a skill is not suitable for the current topic, explain the reason first, then switch to the alternative pipeline.
One article corresponds to one
```
slug
```
, do not mix multiple topics into the same pipeline.
If the user does not pass
```
slug
```
, generate the default
```
slug
```
first, then start the first stage.

If the user does not pass

workspace_root

, use

/root/workspace/data/wechat-pipeline

by default.

Execution Process

Stage 0: Optional Positioning Convergence

If the user gives a broad topic, or this content relies more on brand judgment than keyword research, first use

ai-workflow-brand

to converge the positioning, main line and topic direction.

This stage is an optional enhancement and does not replace the subsequent formal stages.

Stage 1: Topic Selection

Use

keyword-research

Input:

Topic direction given by the user

If the user does not provide

slug

, automatically generate it based on the topic first.

Output:

```
<workspace_root>/00_topics/<slug>.md
```

Minimum requirements:

Provide 10 writable topics
Each topic includes keywords, search intent, target readers
Provide priority
Finally converge to 1 most worth writing topic

Stage 2: Research

Use

seo-content-brief

by default.

Input:

```
<workspace_root>/00_topics/<slug>.md
```

Output:

```
<workspace_root>/01_research/<slug>.md
```

Minimum requirements:

Article objectives
Reader portrait
Core arguments
Structural outline
Evidence points or case suggestions
Title direction

If using the official account quick writing pipeline, switch to

wechat-topic-outline-planner

at this stage to directly generate the official account outline.

Stage 2.5: Optional Pre-writing Calibration

If the current article is knowledge-based judgment content (AI, workflow, cognition, content production, judgment), use

knowledge-article-calibrator

for pre-writing calibration before entering writing.

Input:

```
<workspace_root>/01_research/<slug>.md
```

Output:

The calibration result is written at the end of the research file, or recorded as a separate note

Calibration content:

Misconception identification (many people think X, but actually Y)
Real scenarios (1-3)
Core judgment sentences
Problem recalculation
Suggested structure
Writing risks

If the calibration result shows that the topic is too broad, has no real scenario or lacks core judgment, do not enter writing, go back to the research stage to revise first.

This stage is an optional enhancement. It is triggered only when the article topic clearly belongs to knowledge-based judgment content.

Stage 3: Writing

Use

seo-content-writer

by default.

Input:

```
<workspace_root>/01_research/<slug>.md
```

Output:

```
<workspace_root>/02_drafts/<slug>.md
```

Minimum requirements:

The title has click motivation but is not excessively exaggerated
Clear structure
Have cases or scenarios
There are action suggestions at the end

If using the official account quick writing pipeline, switch to

wechat-article-writer

at this stage.

Stage 3.5: Optional Post-writing Review

If the current article is knowledge-based judgment content, use

knowledge-article-auditor

to review the first draft on a 20-point scale before entering optimization.

Input:

```
<workspace_root>/02_drafts/<slug>.md
```

Output:

Review report (total score, strongest part, biggest problem, score for each item, must be fixed, rewrite order)
If the total score is lower than 12, prioritize fixing the first draft, do not enter format optimization

Scoring criteria:

16-20: Can enter optimization
12-15: Enter optimization but mark items to be fixed
0-11: Return to the writing stage for revision

This stage is an optional enhancement. It is triggered only when the article topic clearly belongs to knowledge-based judgment content.

Stage 4: Optimization

Use

baoyu-format-markdown

Input:

```
<workspace_root>/02_drafts/<slug>.md
```

Output:

```
<workspace_root>/03_polish/<slug>.md
```

Minimum requirements:

Complete the title
Complete the abstract
Adjust the subtitle hierarchy
Organize lists and key emphasis
Complete CTA

Stage 4.5: Optional Entry Optimization

If the draft or optimized draft is already valid, but the title and opening are still too abstract, too conclusion-oriented, and lack click motivation, use

reader-hook

for entry optimization.

Input:

<workspace_root>/02_drafts/<slug>.md

<workspace_root>/03_polish/<slug>.md

Output:

Updated title and opening plan, written back to the current manuscript or recorded as a separate optimization suggestion

This stage does not change the main line of the article, only improves the reader's entry experience.

Stage 5: Distribution Preparation

Use

baoyu-markdown-to-html

Input:

```
<workspace_root>/03_polish/<slug>.md
```

If the user wants to do a brand main line check before converting to HTML, first use

ai-workflow-brand

to review the current manuscript, then continue with distribution preparation.

Output:

```
<workspace_root>/04_publish/<slug>.html
```

Stage 6: Publishing

Only when the user explicitly says "publish", use

baoyu-post-to-wechat

Input:

```
<workspace_root>/04_publish/<slug>.html
```

Output:

Published to WeChat Official Account, or provide login/API selection during the publishing process

Stage Switching Conditions

Only when the following conditions are met can you enter the next stage:

```
00_topics/<slug>.md
```
exists before entering research
```
01_research/<slug>.md
```
exists before entering writing
```
02_drafts/<slug>.md
```
exists before entering optimization
```
03_polish/<slug>.md
```
exists before converting to HTML
```
04_publish/<slug>.html
```
exists and the user explicitly requests publishing before entering official account publishing

Optional enhancement stages do not change the required product requirements of the main stages.

Batch Execution Suggestions

If users want to update weekly or produce in batches, execute in batches according to this rhythm:

Run topic selection uniformly on Monday
Run research uniformly on Tuesday
Run writing uniformly on Wednesday
Run optimization uniformly on Thursday
Run HTML conversion and publishing uniformly on Friday

wechat-pipeline

NPX Install

Tags

SKILL.md Content (Chinese)

WeChat Pipeline

When to use

Allowed Skills

Recommended Enhanced Skills in This Repository

Working Directory

Core Rules

Execution Process

Stage 0: Optional Positioning Convergence

Stage 1: Topic Selection

Stage 2: Research

Stage 2.5: Optional Pre-writing Calibration

Stage 3: Writing

Stage 3.5: Optional Post-writing Review

Stage 4: Optimization

Stage 4.5: Optional Entry Optimization

Stage 5: Distribution Preparation

Stage 6: Publishing

Stage Switching Conditions

Batch Execution Suggestions