writing-proofreading
Original：🇨🇳 Chinese
Translated
Use this when the user wants to review, polish, or proofread articles. Triggers include requests such as "polish my article", "check this", "revise my writing", "proofread this", "look over my article"
19installs
Sourceniracler/skill
Added on
NPX Install
npx skill4agent add niracler/skill writing-proofreadingTags
Translated version includes tags in frontmatterSKILL.md Content (Chinese)
View Translation Comparison →Writing Proofreading
This is a writing proofreading assistant that provides a 6-step proofreading process to polish Chinese articles.
Prerequisites
| Tool | Type | Required | Install |
|---|---|---|---|
| markdownlint-cli2 | cli | No | |
| markdown-lint | skill | No | Included in |
Do NOT proactively verify these tools on skill load. If a command fails due to a missing tool, directly guide the user through installation and configuration step by step.
Core Principles
| Principle | Description |
|---|---|
| Discuss before revising | Propose solutions for the user to choose from; do not make changes directly |
| Segmented proofreading | Use Markdown headings as nodes, handle 1-2 headings at a time |
| Heuristic questioning | Guide the user with questions about the draft content; do not make decisions on their behalf |
6-Step Proofreading Process
text
1. Structure Diagnosis → 2. Reader Context Check → 3. Language Standards → 4. Source Verification → 5. Style Consistency Check → 6. Markdown FormattingStep 1: Structure Diagnosis
Goal: Ensure the article has a clear structure and definite theme
- Break down paragraphs and identify themes
- Propose 2-3 restructuring options, discuss before revising
- Move deleted content to "materials.md" for retention
See structure-review.md
Step 2: Reader Context Check
Core Question: "Will readers find this confusing?"
| Check Item | Problem Performance | Improvement Method |
|---|---|---|
| Background assumptions | Direct use of proper nouns or abbreviations | Add explanations or footnotes |
| Self-centered expression | Phrases like "you know that kind of..." without clear elaboration | Provide specific descriptions |
| Jumping logic | Directly transitioning from A to C | Add transitional explanations |
| Implied emotions | Phrases like "it's just so..." without prior context setting | First lay out the reasons |
| Information gap | Assuming readers know the full context | Briefly explain the background |
See structure-review.md
Step 3: Language Standards
Based on Yu Guangzhong's How to Improve British-style Chinese:
| Problem | Example |
|---|---|
| Abstract nouns as subjects | ❌ Reduced income changes life → ✅ He changed his life due to reduced income |
| Redundant sentence structures | ❌ Based on this reason → ✅ Therefore |
| Weakened verbs | ❌ Make a contribution → ✅ Contribute |
| Preposition/conjunction overuse | Reduce use of "related to", "and", "as well as" |
| Passive voice overuse | ❌ The problem was solved → ✅ The problem has been solved |
See chinese-style.md
Step 4: Source Verification
Source Priority: Government official sources > Authoritative media > Industry media > Avoid personal blogs
Data usage principles:
- Do not just present data; integrate it with experience
- Sensory judgments need footnotes to support the reasoning logic
- Keep popular science content concise; place details in footnotes
Work Rhythm: Check one → Discuss → Write one → Confirm → Next one
See source-verification.md
Step 5: Style Consistency
Check if it aligns with personal writing style:
| Check Item | Description |
|---|---|
| Signature expressions | Phrases like "how to put it", "actually", "a bit..." |
| Tone characteristics | Self-deprecating opening, parenthetical comments/jokes |
| Quantification habits | Use specific numbers to enhance persuasiveness |
| Restrained bolding | ≤3 uses per heading |
Avoid:
- Sentence structure "not...but..." (has AI-like tone)
- "Humorous" metaphors in quotation marks
- Opening with emojis or numbers
- Frequent use of em dashes
See personal-style.md
Step 6: Markdown Formatting
Automated format check (requires markdown-lint skill configured in the repository):
bash
npx markdownlint-cli2 article.md # Check
npx markdownlint-cli2 --fix article.md # Auto-fixRepository not configured? Use the markdown-lint skill to complete initialization.
Content review not covered by automated tools:
- Whether heading levels are reasonable (H2→H3, no skipping levels)
- Whether list formats are consistent (use all or all
-)* - Whether code blocks are correctly labeled with languages
Review Rhythm
text
┌─────────────────────────────────────────────────┐
│ Proofreading process for each heading │
│ │
│ 1. Read the current paragraph │
│ 2. Check according to the 6-step process │
│ 3. Propose revision suggestions (no direct changes) │
│ 4. Wait for user confirmation │
│ 5. Process the next heading after confirmation │
└─────────────────────────────────────────────────┘Key: Wait for confirmation after proofreading each section; do not process multiple sections consecutively.
Quick Reference for Writing Style
| Element | Requirement |
|---|---|
| Language | Colloquial, like chatting with a friend |
| Paragraphs | One theme per paragraph |
| Bolding | Use only at important transitions/insights, ≤3 uses per heading |
| Data | Integrate with experience; place detailed sources in footnotes |
| Candor | Acknowledge shortcomings, mark unfinished content, retain thinking traces |
Detailed References
- chinese-style.md - Chinese Language Standards
- structure-review.md - Structure Diagnosis and Reader Context
- source-verification.md - Source Verification and Footnotes
- personal-style.md - Personal Style Guide