MARKET//SKILLS
Try Mika
中文
SYS.ONLINE
Content / MOD.06 / v2.0.0

WeChat Article Editing Checklist

Use a publication-ready WeChat article editing checklist to repair the reading path, strengthen evidence and Chinese rhythm, align the title and abstract, and surface final human approvals.

WeChat editingArticle structureTitles and abstractsPublication review
MODULE STATUS READY TO INSTALL
VERSION
2.0.0
UPDATED
2026-08-01
LICENSE
MIT
FILES
04
Delegate to Mika ↗100 Mika credits per task, including one revision · See the homepage for the signup offer
INSTALL / wechat-article-editorREADY
npx skills add fffffrost/market-skills --skill wechat-article-editor
MODEL EVIDENCE / v2.0.0

Check the actual test coverage

This skill appears in two-run API tests on synthetic Chinese materials. The reports include failures and require review; installation compatibility is a separate claim.

Use the localization → WeChat handoff brief ↓
WECHAT ARTICLE EDITING CHECKLIST

Edit the reading path before you polish sentences.

A publishable WeChat Official Account article is one aligned system: reader promise, structure, evidence, Chinese rhythm, title, abstract, visual notes, and call to action. Fix that system before line editing hides a broken argument.

01 / MODE

Agree the edit mode

Choose proofread, line edit, structural edit, or source-led reconstruction and protect the author position.

What may change, and what must remain untouched?
02 / PROMISE

State the reader promise

Name the reader, the tension they recognize, the value they receive, and the next action the article supports.

Can the promise be stated in one precise sentence?
03 / PATH

Repair the reading path

Reorder the opening, problem, evidence, implications, objections, and close; remove repeated sections.

Does each section earn the next one?
04 / PROOF

Strengthen credibility

Trace numbers, quotations, product claims, dates, and causal language; flag unsupported or expired statements.

Which claims still need a human owner or source?
05 / RHYTHM

Edit Chinese rhythm

Tighten sentence length, transitions, headings, repetition, and jargon without flattening the author voice.

Is the article easier to follow without sounding generic?
06 / PACKAGE

Align the publishing package

Check title, abstract, body, visual notes, captions, CTA, preview, links, and the final approval queue together.

Do all publishing elements make the same promise?
WORKSHEET / COPY AND COMPLETEFrom draft diagnosis to publication handoff
WECHAT ARTICLE EDITING CHECKLIST

EDIT MODE
Requested mode: proofread / line / structural / reconstruction
Author position to preserve:
Facts or sections that must not change:
Approval owner:

READER PROMISE
Primary reader:
Recognized tension:
Value of reading:
Decision or action after reading:
One-sentence promise:

READING PATH
Opening job:
Section sequence:
Repeated or removable sections:
Evidence placement:
Objection / limitation:
Close and CTA:

PROOF CHECK
Claim | Source | Date | Wording risk | Owner | Status

CHINESE EDIT
[ ] Sentence length and subject are clear
[ ] Headings describe real progression
[ ] Transitions carry the argument
[ ] Jargon and translated phrasing are removed
[ ] Author voice and position are preserved

PUBLISHING PACKAGE
Title options:
Abstract:
Cover / visual note:
In-body image and caption notes:
Links and CTA:
Preview device / account:

FINAL HUMAN CHECKS
[ ] Product and factual approval
[ ] Brand / communications approval
[ ] Copyright and compliance review
[ ] Title, abstract, body, and visuals aligned
[ ] Unknowns and unresolved claims visible

HANDOFF
Change log:
Approval queue:
Publication owner / date:
SYNTHETIC EDIT TRACE

Four repairs that turn a correct draft into a readable article.

This is an illustrative edit trace, not a real client result. The full case keeps the facts synthetic and shows where product approval must interrupt the edit.

OPENINGLead with the reader tension

Replace several paragraphs of internal context with the decision the target reader is already facing.

STRUCTUREMerge repeated benefits

Move proof beside the claim it supports and let each section advance a distinct part of the argument.

CLAIMSStop where facts are missing

Keep dated statements traceable and send unresolved product or performance claims to an explicit owner.

PACKAGEAlign every promise

Make the title, abstract, body, visual notes, and CTA describe the same article instead of five variants.

Open the full synthetic editing case
HANDOFF / LOCALIZATION → WECHAT

Accept the brief before you edit the article.

Check the source version, approved claims, and reader promise before editing. Return missing evidence to its owner; the editing output is a review package, not permission to publish.

One brief travels with the draft
LOCALIZATION → WECHAT EDITING HANDOFF

01 / APPROVED SOURCE
Source title / link / version:
Evidence cutoff / approval owner / approval date:
Approved claim | Source / date | Allowed wording:
Unresolved claim | Missing evidence | Owner:
Preserve these product names, numbers, and author positions:

02 / WECHAT READER BRIEF
Primary reader / local context:
One-sentence reader promise:
Desired action / CTA:
Chinese terminology / terms to avoid:
Opening → section sequence → proof → close:
Localized draft / source-to-draft claim map:

03 / EDITOR ACCEPTANCE
Requested mode: proofread / line / structural / reconstruction
[ ] Source version and approved claims match the draft
[ ] Reader, promise, terminology, and CTA are explicit
[ ] Missing evidence is assigned, not invented
If a check fails: return the gap to its owner before editing that claim.

04 / RETURN FOR HUMAN REVIEW
Edited body / change log / preserved author position:
Title options / abstract / cover and image notes:
Claim | Source / date | Final wording | Reviewer / status:
Unresolved issues / approval queue / publication owner:
[ ] Title, abstract, body, visuals, and CTA make the same promise
[ ] Factual, brand, rights, and publishing-preview checks completed
Final human approval / date: PENDING until explicitly confirmed
Do not publish automatically.
MINIMUM INPUT
  • Chinese draft
  • Factual sources
  • Target reader
  • Account voice
OUTPUT
  • Revised article
  • Titles and abstract
  • Change log
  • Approval queue
BOUNDARY / NOT FOR THIS

Know where the workflow must stop.

  • Does not replace fact checking copyright clearance or formal compliance review
  • Cannot create a credible long-form article without source material
  • Will not manufacture clickbait or silently change the author position
FAILURE MODES

These conditions distort the result.

  • The edit mode and scope are not agreed before rewriting
  • Sentences are polished while the reading path remains repetitive or broken
  • Title abstract body and visual notes drift from the same facts
Report a skill problem ↗
EXECUTION PROTOCOL

How the skill works

  1. 01Confirm the editing mode
  2. 02State the reader promise
  3. 03Repair the reading path
  4. 04Strengthen evidence and Chinese rhythm
  5. 05Build the publishing package
  6. 06Flag final human checks
FIELD REPORT / CASE

See it inside a complete job.

The case preserves task context, source material, execution trace, output excerpts, and human decisions.

CASE.02 / SYNTHETICTurn a translated launch draft into a credible WeChat articleOPEN REPORT ↗
PACKAGE CONTENTS

Inspect the source before installing.

Instructions, templates, compatibility, and dependencies remain in one open directory.

  • ├─SKILL.md
  • ├─agents/openai.yaml
  • ├─listing.yaml
  • ├─references/wechat-edit-checklist.md
View source on GitHub ↗
RELATED / USE THIS TEMPLATE

Connect the final article to the localization workflow.