Article Rewriter

Article processing skill oriented towards "translation + rewriting + publication".

It is not a pure translator, nor is it a revision tool that only polishes wording. When dealing with foreign language originals, mixed-language originals, content that requires structural reorganization, content that needs adaptation to WeChat Official Account/Zhihu/Newsletter, or when users request draft-level output, "understanding the original text" and "producing the final draft" must be handled separately.

Three Modes:

```
quick
```
: Lightweight translation or lightweight rewriting, no active external research, minimize intermediate files
```
standard
```
: Analyze the original text, supplement small amounts of information if necessary, go through explicit draft and critical revision rounds
```
publish
```
: Analysis, verification, reorganization, critique, revision, polishing, expression optimization, quality inspection, produce a directly publishable version

Default Mode:

standard

Input Types

```
inline text
```
: Users directly paste the main text
```
file path
```
: Read local files
```
URL
```
: Capture the main text before processing (prioritize WebReader; if failed, try reading with
```
https://r.jina.ai/{url}
```
; if still failed, try using
```
https://defuddle.md/{url}
```
; if all fail, clearly state that content cannot be obtained)

Default Values

Setting	Default Value	Description
Output Language	`zh-CN`	Unified final output in Chinese
Mode	`standard`	Used when not specified by users
Platform	`generic`	Switch to corresponding preset if users mention WeChat Official Account/Zhihu/Newsletter
Number of Titles	`5`	Provide 5 title candidates when not specified by users
Research Scope	`2-4` topics	Extend to `4-6` in `publish` mode
Output Directory	`rewrites/{slug}-{timestamp}/`	All intermediate files and final drafts are stored here uniformly
Long Article Threshold	`> 2500` English words or `> 4000` Chinese characters	Prioritize chunked writing and unified review when exceeded

Modes

Mode	Trigger Words	Core Steps	Applicable Scenarios
Quick	"Simple polish", "Quick revision", "No external research"	Constraint confirmation → Terminology unification (if needed) → Direct draft generation	Short articles, light polishing, users explicitly request no external research
Standard	Default	Analysis → Selective research → Prompt snapshot → Draft → Critique → Revision → Expression optimization → Final draft	Most article rewriting needs, especially "translate and rewrite"
Publish	"In-depth rewrite", "WeChat Official Account draft", "Suitable for publication", "Supplement information and rewrite"	Analysis → Verification → Reorganization → Prompt snapshot → Draft → Critique → Revision → Polishing → Expression optimization → Quality inspection → Final draft	Needs publication, fact-sensitive content, high style requirements or long article tasks

Automatic Judgment Rules:

Use
```
quick
```
when users explicitly say "no external research" or "only revise expression"
Use
```
publish
```
when users explicitly request "publish on WeChat Official Account/Zhihu/Newsletter", "in-depth rewrite", "supplement information" or "like a formal article"
Use at least
```
standard
```
when the task involves obvious translation difficulties, long articles, or users request "draft-level Chinese"
Use
```
standard
```
by default in other cases

Output Directory

Create an output directory for each task:

rewrites/{slug}-{timestamp}/

File	When Needed	Description
`source.md`	All tasks	Original content after saving to disk
`00-brief.md`	All tasks	Task constraints, platform, audience, length, retrieval boundaries, whether reorganization is allowed
`01-analysis.md`	`standard` / `publish`	Topic, structure, audience, reserved items, difficulties, comprehension barriers, rewriting strategies
`01-terms.md`	When there is translation or dense terminology	Terminology table for this task, recommended translations, forbidden translations, pending translations
`02-research.md`	When external research is conducted	External materials, fact verification, conflicting information, quotable key points
`03-outline.md`	`publish` or obvious reorganization needed	New structure, outline, title angles, narrative order
`04-prompt.md`	Default for non-trivial tasks	Writing instruction snapshot, reused for drafting, chunking and subsequent revisions
`05-draft.md`	`standard` / `publish`	First draft; include translator notes if necessary
`06-critique.md`	`standard` / `publish`	Diagnose problems without directly revising the text
`07-revision.md`	`standard` / `publish`	Revised draft after addressing critique comments
`08-polish.md`	`publish`	Polished draft after localization, rhythm adjustment, title optimization and platform adaptation
`09-expression.md`	Non-trivial tasks in `standard` / `publish`	Expression optimization draft after removing translationese, AI tone, clichés and mechanical connections
`qa.md`	`publish` or fact-sensitive tasks	Final quality inspection checklist and residual risks
`rewrite.md`	All tasks	Final deliverable

If users only request direct results in the chat, still save

rewrite.md

by default and provide the path in the response.

Platforms and Writing Styles

Do not hardcode platforms, paragraph rhythms or title styles in the main file. Read on demand:

[references/style-presets.md]: Writing style and title constraints for WeChat Official Account, Zhihu, Newsletter and generic versions
[references/glossary-en-zh.md]: Special translations for English originals or mixed Chinese-English materials
[references/quality-rubric.md]: Fixed inspection dimensions for critique drafts and final quality inspection
[references/expression-optimizer.md]: Patterns of translationese, AI tone and clichés to be cleaned up during final expression optimization

Selection Logic:

Prioritize using corresponding presets when users explicitly specify a platform
When no platform is specified, first judge based on original text type and target audience; use
```
generic
```
if still unclear
Technical, commercial and social topics can have narrative elements, but avoid forced "鸡血化 (overly motivational)" or "爆款化 (viral-style)" styles

Terminology Handling

Terminology unification must be completed before rewriting if any of the following situations apply:

The original text is in English
The original text is mixed Chinese-English
The original text involves high-frequency proper nouns in AI, product, business or technical fields
Users explicitly request "translate and rewrite"

Processing Sequence:

Prioritize reading the built-in terminology table [references/glossary-en-zh.md]
Extract additional proper nouns, abbreviations, product names and methodology terms from the original text
Form a session-specific terminology table for this task and write it to
```
01-terms.md
```
Mark recommended translations, forbidden translations, retained original terms and pending items
Subsequent drafts, critiques and revisions must follow
```
01-terms.md
```
and must not deviate arbitrarily

Implementation Principles:

Use standard Chinese directly for common and established terms
Prioritize following the built-in terminology table for terms that are easily mistranslated or have large style differences

When first appearing, use

Chinese (English)

Chinese (English original, brief explanation)

If multiple reasonable translations exist for a term, choose the one most suitable for the target platform and audience, and maintain consistency throughout the text
Rewriting allows sentence reorganization, but do not "lose" key terms or convert them to overly colloquial expressions

Workflow

Step 1: Obtain Constraints and Write to

00-brief.md

Prioritize extracting from the current conversation; do not repeatedly ask for default values. At least confirm:

Input source: text, file, URL
User goal: polish, expand, translate and rewrite, publishable draft, platform adaptation
Whether external retrieval is allowed
Whether to retain the original structure
Whether to control length
Target platform and audience
Fact sensitivity: normal / medium / high

If users do not specify:

Default to "supplement small amounts of information if necessary", but avoid excessive searching for static content
Default to allowing structural reorganization, but retain the core arguments of the original text
Default to providing 5 title candidates

00-brief.md

should record:

Source type
Goal
Platform
Audience
Length target
Research boundary
Preserve structure: yes / no / partial
Fact sensitivity
Output promise

Step 2: Save Original Text to Disk and Create Output Directory

Save all input content to
```
source.md
```
uniformly
Create output directory
```
rewrites/{slug}-{timestamp}/
```
Detect the language of the original text
If the original text is not in Chinese, first load the built-in terminology table and extract session-specific terms, then write to
```
01-terms.md
```
If the original text is long, first determine chunk boundaries and merging strategies before entering the drafting stage

Requirements:

For URL input, prioritize extracting the main text to avoid contamination from navigation, recommendation sections and comment areas
If file or URL extraction fails, clearly state the blocking point; if still proceedable, fall back to the main text provided by the user
Chunk by semantic boundaries, not mechanically by word count

Step 3: Analyze Original Text and Write to

01-analysis.md

01-analysis.md

must be produced in

standard

and

publish

modes. At least include:

Original text topic, core arguments, author's intent
Inferred target audience
Original text structure breakdown
Facts, figures, cases and citations that must be retained
Key terms and recommended translations
Reader comprehension barriers: background knowledge gaps, pronoun references, long sentences, jumpy arguments
Metaphors and cultural mappings: which metaphors should be retained, translated, explained or downplayed
Tone target: restrained / narrative / comment / methodological / press release
Optimizable points: overly long, repetitive, jumpy, vague, outdated facts, conclusions too early or too late
Rewriting strategy: conservative rewriting / structural reorganization / secondary creation after translation

If the original text is already well-written, clearly state in the analysis that "optimization should focus on incremental improvements and readability" instead of forced subversion.

Step 4: Research and Fact Verification

When to create

02-research.md

Users explicitly request supplementary materials, latest information, cases or data
The original text contains obviously time-sensitive content
Figures, studies or company information in the original text may be outdated
The topic itself requires basic fact verification

Read on demand:

[references/research-rules.md]: Retrieval scope, source priority, conflict handling, citation format

Implementation Principles:

```
quick
```
mode defaults to no active external research
Skip external research if users explicitly prohibit it, and note in the final result "This rewrite is based on the user-provided original text with no additional external materials"
```
standard
```
mode only searches for key information that can significantly improve article credibility
```
publish
```
mode must separate "external facts", "author's opinions" and "your inferences"
Research files only record "facts and sources", do not mix in language issues

Step 5: Plan New Structure

03-outline.md

must be written in the following cases:

```
publish
```
mode
The original text structure is obviously chaotic
Users request platform adaptation with significant style changes
Need to convert from translation to "final draft suitable for Chinese publication"

At least include:

Title directions: insight-based / benefit-based / counterintuitive / scenario-based / question-based
Opening strategies: story, scenario, contrast, question, conclusion first
Main body paragraph order
Purpose of each paragraph
Closing actions: summary, reminder, method, next-step suggestions

standard

mode does not need to save the outline to disk separately, but must determine the structure before writing.

Step 6: Assemble Prompt Snapshot and Write to

04-prompt.md

04-prompt.md

is produced by default for non-trivial tasks. It is not a final draft for users, but a unified instruction reused for subsequent drafting, chunking and revisions.

At least clearly state:

Task goal
Output language and platform
Target audience
Information that must be retained
Allowable degree of reorganization
Terminology constraints
Prohibited items
Research conclusions or time boundaries
Writing style requirements
Title requirements

If the task requires chunking:

Each chunk reuses the same
```
04-prompt.md
```
Each chunk only processes its own main text and does not invent global conclusions on its own
Must conduct a unified critique and revision of the merged full draft

Step 7: Generate

05-draft.md

05-draft.md

is the first draft, which does not need to be perfect, but must stabilize the framework and information of the original text first.

Implementation Principles:

If the original text is in a foreign language, first ensure complete information, accurate relationships and stable terminology in the first draft
Allow short translator notes to record difficulties, ambiguities and trade-offs
Avoid forced wit or rhetorical stacking in the drafting stage
If it is a chunked task, first obtain the first draft of all chunks, then merge into a unified
```
05-draft.md
```

Step 8: Generate

06-critique.md

06-critique.md

only diagnoses problems and does not directly revise the text. Prioritize reading [references/quality-rubric.md].

At least check item by item from the following dimensions:

Accuracy: Whether there is mistranslation, omission, over-translation or relationship misalignment
Completeness: Whether key constraints, facts and examples are missing
Natural Chinese: Whether there are Europeanized syntax, literal translations or awkward collocations
Terminology: Whether terminology is consistent and first-time explanations are reasonable
Structure: Whether paragraph order and causal chains are clear
Register / Platform Fit: Whether it conforms to WeChat Official Account, Zhihu, Newsletter or formal writing styles
Fact Boundary: Whether inferences and facts are confused, and time-sensitive information is properly handled
Title / Framing: Whether titles, openings and text promises are consistent

Writing Requirements:

Point out problems and their impacts item by item
Prioritize stating "what is wrong, why it is wrong, and how to revise it"
Do not rewrite the full text directly in the critique draft

Step 9: Generate

07-revision.md

Address all problems in

06-critique.md

to get a revised draft with more stable structure and expression.

Implementation Principles:

First revise accuracy, completeness and logic, then revise language and rhythm
If there are conflicting suggestions in the critique, prioritize facts and clarity
Do not introduce new facts during revision unless they have been verified in
```
02-research.md
```

Step 10: Generate

08-polish.md

Polishing must be done in

publish

mode, and should also be done in

standard

mode when users request "like a final draft" or "directly publishable".

Polishing only addresses the following problems:

Convert translationese to natural Chinese
Smooth out paragraph rhythm and transitions
Adjust the attractiveness and restraint of titles, openings and closings
Clean up repetitive expressions, vague rhetoric and over-explanations
Unify subheadings, punctuation, formatting and chapter density

Do not do the following during polishing:

Reinvent viewpoints
Introduce unverified facts
Delete key qualifiers for the sake of "smoothness"

Step 11: Generate

09-expression.md

After the structure, facts and rhythm are stable, conduct a separate "expression optimization" round. Prioritize reading [references/expression-optimizer.md].

This step only handles the expression layer and does not revise arguments or facts. Core goals:

Remove translationese, AI tone and propaganda tone
Delete vague exaggerations, mechanical conjunctions and formulaic three-part structures
Convert vague attributions to specific attributions or conservative expressions
Tighten excessive rhetoric, slogan sentences and sentences that look like quoted golden lines
Make paragraphs look like Chinese written by a real author instead of a "very capable model"

Key Inspection Points:

Overemphasis on significance, historical status and grand trends
Conjunction crutches such as "此外 / 值得注意的是 / 不仅如此 / 归根结底" (furthermore / it is worth noting that / not only that / in the final analysis)
Negative parallel structures such as "不仅……而且……" (not only...but also...) and "这不仅是……更是……" (this is not only...but also...)
Stilted three-item parallelism, false sense of completeness
Vague attributions such as "experts believe", "it is widely believed in the industry", "some opinions point out"
Excessive use of dashes, bold text, abstract nouns and slogan-style closings
Frequent synonym replacement to avoid repetition, leading to terminology or subject drift

Implementation Principles:

Retain the original meaning; do not add opinions in the name of "human touch"
The more formal the platform, the more restrained the style; do not forcefully convert formal writing styles to social media tones
Allow natural rhythm changes, but do not deliberately "perform" a relaxed tone
If the original text is already a highly restrained technical or formal style, the optimization goal is to remove mechanicalness, not add emotion

Step 12: Quality Inspection and Save Final Draft

qa.md

must be written for

publish

mode and fact-sensitive tasks, at least including:

Whether there is mistranslation, omission or over-translation
Whether there are unverified new facts
Whether terminology is consistent throughout
Whether titles accurately reflect the main text
Whether the most important facts, figures, cases and citations of the original text are retained
Whether there are still areas requiring conservative expressions
Whether
```
09-expression.md
```
only revised expressions without altering facts and judgments

The final draft is always saved to

rewrite.md

09-expression.md

was created:

```
rewrite.md
```
is based on
```
09-expression.md
```

If no separate expression optimization was done but

08-polish.md

was created:

```
rewrite.md
```
is based on
```
08-polish.md
```

If no separate polishing was done:

```
rewrite.md
```
is based on
```
07-revision.md
```

Step 13: Generate Title Candidates

Provide 5 title candidates by default, prioritizing different angles instead of just changing a few words:

Insight-based
Benefit-based
Counterintuitive
Scenario-based
Question-based

Title Rules:

Must accurately reflect the core value of the main text
Do not fabricate figures, exaggerate conclusions or create non-existent urgency
The more formal the platform, the more restrained the title
The angles of titles in the same group must be significantly different

Skip this step if users explicitly say "no titles needed".

Long Article and Chunking Strategy

Do not directly translate long articles in one go. Adopt the approach of "unified constraints, local chunking, overall review".

Implementation Sequence:

First complete

00-brief.md

01-analysis.md

01-terms.md

and

04-prompt.md

Chunk by semantic boundaries, not mechanically by character count
Each chunk shares the same terminology table and prompt snapshot
Merge all chunk first drafts into
```
05-draft.md
```
Conduct unified
```
06-critique.md
```
for the merged full draft
After unified revision, decide whether to enter
```
08-polish.md
```
Regardless of whether separate polishing is done, always conduct expression optimization on the merged full draft before outputting
```
rewrite.md
```

Special Notes:

Chunking only solves the context window problem and does not mean each chunk can set its own tone independently
All global judgments, titles, openings and closings should be handled uniformly after merging
Must check for terminology drift, repeated explanations and inconsistent statements in the merged draft
Expression optimization must be done on the merged full text, not separately "humanized" for each chunk

Final Output Format

rewrite.md

uses the following structure by default:

markdown

## Title Candidates

1. Title 1
2. Title 2
3. Title 3
4. Title 4
5. Title 5

---

## Main Text

[Rewritten full article]

---

## Reference Sources

- [Source Title](Link)
- [Source Title](Link)

---

## Rewrite Notes

- Mode: standard
- Platform: wechat
- Supplementary external materials: Yes
- Terminology table used: Yes
- Critique and revision conducted: Yes
- Expression optimization conducted: Yes

If no external research was done, change "Reference Sources" to:

markdown

## Reference Sources

- This rewrite is based on the user-provided original text with no additional external materials

Quality Threshold

Information density should be higher than the original text, not just rephrasing
If expanding, new content should either explain key concepts or supplement cases/data/boundaries
Fact-sensitive content should be verified first; use conservative expressions if uncertain
The style should have a human touch, but avoid performative sentimentality
If the original text is already high-quality, use "precision polishing" instead of "rewriting"
Tasks involving translation must include at least one explicit critique and revision round
Long articles or chunked tasks must include a unified review of the merged full draft
Non-trivial tasks must undergo a separate expression optimization round before final delivery

Prohibited Items

Do not package unverified information as "latest research shows"
Do not distort conclusions to create viral potential
Do not copy large sections of the original text with only word substitutions
Do not stack vague rhetoric, clichés or excessive exclamation marks
Do not assume all articles are suitable for "viral titles"
Do not rewrite the full text directly in
```
06-critique.md
```
and confuse diagnosis with revision
Do not allow
```
08-polish.md
```
to become another round of unbounded rewriting
Do not allow
```
09-expression.md
```
to alter facts, positions or information density in the name of "expression optimization"

article-rewriter

NPX Install

Tags

SKILL.md Content (Chinese)

Article Rewriter

Input Types

Default Values

Modes

Output Directory

Platforms and Writing Styles

Terminology Handling

Workflow

Step 1: Obtain Constraints and Write to
`00-brief.md`

Step 2: Save Original Text to Disk and Create Output Directory

Step 3: Analyze Original Text and Write to
`01-analysis.md`

Step 4: Research and Fact Verification

Step 5: Plan New Structure

Step 6: Assemble Prompt Snapshot and Write to
`04-prompt.md`

Step 7: Generate
`05-draft.md`

Step 8: Generate
`06-critique.md`

Step 9: Generate
`07-revision.md`

Step 10: Generate
`08-polish.md`

Step 11: Generate
`09-expression.md`

Step 12: Quality Inspection and Save Final Draft

Step 13: Generate Title Candidates

Long Article and Chunking Strategy

Final Output Format

Quality Threshold

Prohibited Items