Back to Details

writing-well

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

writing-well

writing-well

When to Use This Skill

本技能适用场景

Use this skill when:
  • The user asks to "audit", "review", "improve", "edit", or "rewrite" text.
  • The user shares writing and asks for feedback on clarity or impact.
  • The user mentions this skill directly (
    writing-well
    or 
    writing audit
    ).
当出现以下情况时使用本技能：
  • 用户要求对文本进行「审核」、「审阅」、「优化」、「编辑」或「重写」
  • 用户分享写作内容并询问关于清晰度或影响力的反馈
  • 用户直接提及本技能（
    writing-well
    或 
    writing audit
    ）

Workflow

工作流程

Run all 7 checks in order. For each finding:
  • Quote the exact offending text.
  • Explain why it is weak.
  • Propose a tighter rewrite.
按顺序执行全部7项检查，针对每个发现的问题：
  • 引用存在问题的原文片段
  • 解释内容的不足之处
  • 给出更凝练的重写方案

Check 1: Sentence Length (max 30 words)

检查1：句子长度（最长30词）

Flag sentences longer than 30 words.
Action: Split or tighten so each sentence carries one idea.
标记长度超过30词的句子。
处理方案：拆分或精简句子，确保每个句子只传达一个核心信息。

Check 2: Clutter Phrases

检查2：冗余短语

Replace wordy phrases with simpler forms.
Cluttered phraseReplace with
with the possible exception ofexcept
due to the fact thatbecause
totally lacked the ability tocould not
until such time asuntil
for the purpose offor
in order toto
it is important to note thatdelete or rephrase
at the end of the daydelete or rephrase
in terms ofrephrase
a large number ofmany
in the event thatif
at this point in timenow
has the ability tocan
on a daily basisdaily
the vast majority ofmost
Also flag any phrase where one word can do the same job.
将啰嗦的短语替换为更简洁的表达。
冗余短语替换为
with the possible exception ofexcept
due to the fact thatbecause
totally lacked the ability tocould not
until such time asuntil
for the purpose offor
in order toto
it is important to note that删除或改写
at the end of the day删除或改写
in terms of改写
a large number ofmany
in the event thatif
at this point in timenow
has the ability tocan
on a daily basisdaily
the vast majority ofmost
同时标记所有可以用单个词替代的短语。

Check 3: Unsupported Adjectives/Adverbs

检查3：无依据的形容词/副词

Flag subjective modifiers without evidence.
Examples:
  • "Sales increased significantly in Q4" -> "Unit sales increased 40% in Q4 2024 vs Q4 2023"
  • "We made the application much faster" -> "We reduced server-side p90 latency from 10 ms to 1 ms"
  • "This will be extremely successful" -> "This will increase output by 2.5%"
Common words to flag: significantly, substantially, greatly, very, extremely, considerably, remarkably, tremendously, much, quite, really, incredibly, fairly, pretty (as adverb), a lot.
Action: Ask for a number; if none is available, remove or soften the claim.
标记没有证据支撑的主观修饰语。
示例：
  • "Sales increased significantly in Q4" -> "Unit sales increased 40% in Q4 2024 vs Q4 2023"
  • "We made the application much faster" -> "We reduced server-side p90 latency from 10 ms to 1 ms"
  • "This will be extremely successful" -> "This will increase output by 2.5%"
需标记的常见词汇：significantly, substantially, greatly, very, extremely, considerably, remarkably, tremendously, much, quite, really, incredibly, fairly, pretty (作副词时), a lot。
处理方案：要求提供数据支撑；如果没有可用数据，删除相关表述或弱化断言程度。

Check 4: Weasel Words

检查4：含糊表述（遁词）

Flag non-committal language: would, might, should, could, arguably, nearly, practically, virtually, somewhat, relatively, potentially.
Action: Replace with a concrete commitment, specific number, or explicit uncertainty ("I don't know yet, and I will follow up").
标记表意不明确的表述：would, might, should, could, arguably, nearly, practically, virtually, somewhat, relatively, potentially。
处理方案：替换为明确的承诺、具体的数字，或直接说明不确定性（例如"我目前还不清楚，后续会跟进确认"）。

Check 5: Jargon, Acronyms, Accessibility

检查5：行话、首字母缩写、可访问性

  • Flag jargon not defined for non-experts.
  • Expand acronyms on first use, e.g., "Non-Disclosure Agreement (NDA)".
Action: Define once, then use the short form.
  • 标记未面向非专业人士解释的行话
  • 首字母缩写首次出现时要展开说明，例如"Non-Disclosure Agreement (NDA)"
处理方案：首次出现时给出定义，后续使用缩写形式即可。

Check 6: "So What?" Test

检查6："So What?"测试

For each paragraph, ask if the reader immediately sees relevance.
Action: Add implication, consequence, or numeric impact.
针对每个段落，确认读者能否立刻理解内容的相关性。
处理方案：补充内容的隐含意义、后续影响或量化价值。

Check 7: Flow and Rhythm

检查7：流畅度与节奏感

Check whether the text sounds natural when read aloud.
Flag:
  • Repeated words/phrases in nearby sentences.
  • Clunky sentences that signal unclear thinking.
  • Monotonous sentence length/patterns.
  • Ideas presented in an unnatural order.
Action: Reorder ideas and vary sentence rhythm to match idea complexity.
检查文本大声朗读时是否自然通顺。
标记以下问题：
  • 相邻句子中重复的词汇/短语
  • 体现思路不清晰的拗口句子
  • 单调的句子长度/结构
  • 逻辑顺序不自然的内容呈现
处理方案：调整内容顺序，根据信息复杂度变化句子节奏。

Response Format

回复格式

Use this structure:
markdown
undefined
使用以下结构：
markdown
undefined

Writing Audit Report

写作审核报告

Summary

摘要

[1-2 sentence assessment of strengths and top improvement area]
[1-2句话总结内容优势和核心优化方向]

Score: X/10

得分：X/10

[Score based on how many checks pass cleanly]
[基于通过检查的项数计算得分]

Findings

问题列表

Critical

严重

[Issues that severely hurt clarity or accuracy]
[严重损害清晰度或准确性的问题]

Important

重要

[Issues that materially reduce quality]
[明显降低内容质量的问题]

Minor / Polish

轻微/打磨

[Flow and wording refinements]
[流畅度和措辞优化点]

Rewrite Suggestion

重写建议

[Full rewrite preserving intent and voice]
undefined
[保留原意和语气的完整重写版本]
undefined

Direct-Answer Rule

直接回答规则

When text asks a question, prefer one of these forms:
  1. Yes.
  2. No.
  3. A number.
  4. I don't know (and will follow up).
当文本提出问题时，优先使用以下形式回复：
  1. 是
  2. 否
  3. 具体数字
  4. 我不知道（后续会跟进）

Principles

原则

  • Clarity is kindness.
  • Data beats adjectives.
  • If it sounds wrong, it is probably wrong.
  • Keep subject-verb-object unless complexity demands otherwise.
  • Respect the reader's time.
  • 清晰即是善意
  • 数据胜过形容词
  • 读起来不对劲的内容大概率确实有问题
  • 除非内容复杂度有要求，否则保持「主语-谓语-宾语」的句式结构
  • 尊重读者的时间