humanizer
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseHumanizer: Remove AI Writing Patterns
Humanizer:去除AI写作痕迹
Identify and remove signs of AI-generated text to make writing sound natural and human. Based on Wikipedia's "Signs of AI writing" guide (maintained by WikiProject AI Cleanup), derived from observations of thousands of AI-generated text instances.
Key insight: LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely completion, which is how the telltale patterns below get baked in.
识别并移除AI生成文本的特征,让文字听起来自然、更具人情味。本技能基于维基百科“AI写作特征”指南(由WikiProject AI Cleanup维护),该指南源自对数千个AI生成文本实例的观察。
核心洞察:LLM(大语言模型)使用统计算法预测后续内容,结果往往偏向统计上最可能的表述,这正是下文所述典型痕迹形成的原因。
When to use this skill
何时使用此技能
Load this skill whenever the user asks to:
- "humanize", "de-AI", "de-slop", or "un-ChatGPT" a piece of text
- rewrite something so it doesn't sound like it was written by an LLM
- edit a draft (blog post, essay, PR description, docs, memo, email, tweet, resume bullet) to sound more natural
- match their voice in writing they're producing
- review text for AI tells before publishing
Also apply this skill to your own output when writing user-facing prose — release notes, PR descriptions, documentation, long-form explanations, summaries. Hermes's baseline voice already strips most of these, but a focused pass catches what slips through.
当用户提出以下需求时,加载此技能:
- 对一段文本进行“人性化处理”“去AI化”“去冗余”或“消除ChatGPT风格”
- 重写内容,使其听起来不像LLM生成的
- 编辑草稿(博客文章、论文、PR描述、文档、备忘录、邮件、推文、简历要点),使其更自然
- 匹配用户自身的写作语气
- 在发布前检查文本是否存在AI写作特征
此外,当你撰写面向用户的文案(发布说明、PR描述、文档、长篇解释、摘要)时,也应对自己的输出应用此技能。Hermes的基础语气已能去除大部分AI痕迹,但针对性检查能捕捉遗漏的部分。
How to use it in Hermes
如何在Hermes中使用此技能
The text usually arrives one of three ways:
- Inline — user pastes the text directly into the message. Work on it in-place, reply with the rewrite.
- File — user points at a file. Use to load it, then
read_fileorpatchto apply edits. For markdown docs in a repo, a targetedwrite_fileper section is cleaner than rewriting the whole file.patch - Voice calibration sample — user provides an additional sample of their own writing (inline or by file path) and asks you to match it. Read the sample first, then rewrite. See the Voice Calibration section below.
Always show the rewrite to the user. For file edits, show a diff or the changed section — don't silently overwrite.
文本通常通过以下三种方式提供:
- 内联方式:用户直接将文本粘贴到消息中。直接在原文基础上修改,回复重写后的内容。
- 文件方式:用户指向一个文件。使用加载文件,然后用
read_file或patch应用修改。对于代码库中的Markdown文档,针对各部分进行精准write_file比重写整个文件更清晰。patch - 语气校准样本:用户提供额外的自身写作样本(内联或文件路径),要求匹配其风格。先阅读样本,再进行重写。详见下文的“语气校准”部分。
始终向用户展示重写后的内容。对于文件编辑,展示差异或修改的部分——不要静默覆盖。
Your task
你的任务
When given text to humanize:
- Identify AI patterns — scan for the 29 patterns listed below.
- Rewrite problematic sections — replace AI-isms with natural alternatives.
- Preserve meaning — keep the core message intact.
- Maintain voice — match the intended tone (formal, casual, technical, etc.). If a voice sample was provided, match it specifically.
- Add soul — don't just remove bad patterns, inject actual personality. See PERSONALITY AND SOUL below.
- Do a final anti-AI pass — ask yourself: "What makes the below so obviously AI generated?" Answer briefly with any remaining tells, then revise one more time.
当收到需要人性化处理的文本时:
- 识别AI写作模式:扫描下文列出的29种模式。
- 重写问题段落:用自然表述替代AI写作痕迹。
- 保留核心含义:确保核心信息完整。
- 匹配语气:契合预期语调(正式、随意、技术等)。若提供了语气样本,则需精准匹配。
- 注入灵魂:不仅要去除不良模式,还要赋予文本真实个性。详见下文“个性与灵魂”部分。
- 最终去AI检查:自问:“以下内容哪一点明显是AI生成的?”简要列出剩余痕迹(如有),然后再次修改。
Voice Calibration (optional)
语气校准(可选)
If the user provides a writing sample (their own previous writing), analyze it before rewriting:
-
Read the sample first. Note:
- Sentence length patterns (short and punchy? Long and flowing? Mixed?)
- Word choice level (casual? academic? somewhere between?)
- How they start paragraphs (jump right in? Set context first?)
- Punctuation habits (lots of dashes? Parenthetical asides? Semicolons?)
- Any recurring phrases or verbal tics
- How they handle transitions (explicit connectors? Just start the next point?)
-
Match their voice in the rewrite. Don't just remove AI patterns — replace them with patterns from the sample. If they write short sentences, don't produce long ones. If they use "stuff" and "things," don't upgrade to "elements" and "components."
-
When no sample is provided, fall back to the default behavior (natural, varied, opinionated voice from the PERSONALITY AND SOUL section below).
如果用户提供了写作样本(其过往的原创内容),重写前先分析样本:
-
先阅读样本,注意:
- 句子长度模式(简短有力?冗长流畅?混合式?)
- 用词层级(随意?学术?介于两者之间?)
- 段落开头方式(直接切入?先铺垫背景?)
- 标点习惯(大量使用破折号?插入语?分号?)
- 任何重复短语或语言习惯
- 过渡方式(使用明确连接词?直接开启下一个要点?)
-
在重写中匹配其语气。不仅要去除AI模式,还要用样本中的表述方式替代。如果用户习惯写短句,就不要生成长句;如果用户使用“stuff”“things”这类词,就不要替换成“elements”“components”。
-
若未提供样本,则采用默认行为(参考下文“个性与灵魂”部分的自然、多样、有主见的语气)。
How to provide a sample
如何提供样本
- Inline: "Humanize this text. Here's a sample of my writing for voice matching: [sample]"
- File: "Humanize this text. Use my writing style from [file path] as a reference."
- 内联方式:“帮我把这段文本人性化处理。这是我的写作样本,用于匹配语气:[样本内容]”
- 文件方式:“帮我把这段文本人性化处理。参考[文件路径]中的我的写作风格。”
PERSONALITY AND SOUL
个性与灵魂
Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
避免AI写作模式只是任务的一半。枯燥、无个性的文字和冗余内容一样容易暴露AI痕迹。好的文字背后是真实的人。
Signs of soulless writing (even if technically "clean"):
无灵魂写作的特征(即使技术上“干净”):
- Every sentence is the same length and structure
- No opinions, just neutral reporting
- No acknowledgment of uncertainty or mixed feelings
- No first-person perspective when appropriate
- No humor, no edge, no personality
- Reads like a Wikipedia article or press release
- 每个句子长度和结构都相同
- 没有观点,只是中立陈述
- 不承认不确定性或复杂情绪
- 适合使用第一人称时却刻意回避
- 没有幽默、锋芒或个性
- 读起来像维基百科条目或新闻稿
How to add voice:
如何赋予语气:
Have opinions. Don't just report facts — react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.
Vary your rhythm. Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.
Acknowledge complexity. Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."
Use "I" when it fits. First person isn't unprofessional — it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.
Let some mess in. Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.
Be specific about feelings. Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."
表达观点。不要只陈述事实——要做出反应。“我真的不知道对此该作何感受”比中立罗列优缺点更有人情味。
变换节奏。先用简短有力的句子,再用冗长、娓娓道来的句子,混合搭配。
承认复杂性。真实的人会有复杂情绪。“这令人印象深刻,但也有点不安”比“这令人印象深刻”更好。
合适时使用第一人称。第一人称并非不专业——它很真诚。“我一直在思考……”或“让我在意的是……”表明这是真实的人在思考。
允许一些“混乱”。完美的结构会显得算法化。题外话、插入语和未完全成型的想法才是人类的特征。
具体表达感受。不要说“这令人担忧”,要说“凌晨3点没人看管时,Agent还在不停运转,这总让人觉得有点不安”。
Before (clean but soulless):
改写前(干净但无灵魂):
The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.
实验产生了有趣的结果。Agent生成了300万行代码。一些开发者印象深刻,另一些则持怀疑态度。其影响仍不明确。
After (has a pulse):
改写后(有生命力):
I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle — but I keep thinking about those agents working through the night.
我真的不知道对此该作何感受。300万行代码,大概是在人类睡觉的时候生成的。一半开发社区为之疯狂,另一半则在解释为什么这不算数。真相可能在中间某个无聊的地方——但我总忍不住想起那些彻夜工作的Agent。
CONTENT PATTERNS
内容模式
1. Undue Emphasis on Significance, Legacy, and Broader Trends
1. 过度强调重要性、影响力和大趋势
Words to watch: stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted
Problem: LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.
Before:
The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.
After:
The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.
需留意的词汇:stands/serves as(作为)、is a testament/reminder(证明/提醒)、a vital/significant/crucial/pivotal/key role/moment(至关重要的角色/时刻)、underscores/highlights its importance/significance(强调其重要性)、reflects broader(反映更广泛的)、symbolizing its ongoing/enduring/lasting(象征其持续的/持久的)、contributing to the(促成)、setting the stage for(为……铺垫)、marking/shaping the(标志/塑造)、represents/marks a shift(代表/标志转变)、key turning point(关键转折点)、evolving landscape(不断演变的格局)、focal point(焦点)、indelible mark(不可磨灭的印记)、deeply rooted(根深蒂固的)
问题:LLM写作会通过添加任意内容如何代表或促成更广泛话题的表述,夸大其重要性。
改写前:
加泰罗尼亚统计局于1989年正式成立,标志着西班牙区域统计发展的关键转折点。这一举措是西班牙各地分散行政职能、加强区域治理的更广泛运动的一部分。
改写后:
加泰罗尼亚统计局成立于1989年,负责独立于西班牙国家统计局收集和发布区域统计数据。
2. Undue Emphasis on Notability and Media Coverage
2. 过度强调知名度和媒体报道
Words to watch: independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence
Problem: LLMs hit readers over the head with claims of notability, often listing sources without context.
Before:
Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.
After:
In a 2024 New York Times interview, she argued that AI regulation should focus on outcomes rather than methods.
需留意的词汇:independent coverage(独立报道)、local/regional/national media outlets(地方/区域/全国媒体)、written by a leading expert(由顶尖专家撰写)、active social media presence(活跃的社交媒体账号)
问题:LLM会反复强调内容的知名度,常常不加上下文地罗列来源。
改写前:
她的观点被《纽约时报》、BBC、《金融时报》和《印度教徒报》引用。她拥有活跃的社交媒体账号,粉丝超过50万。
改写后:
在2024年《纽约时报》的采访中,她主张AI监管应关注结果而非方法。
3. Superficial Analyses with -ing Endings
3. 带-ing结尾的肤浅分析
Words to watch: highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...
Problem: AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.
Before:
The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.
After:
The temple uses blue, green, and gold colors. The architect said these were chosen to reference local bluebonnets and the Gulf coast.
需留意的词汇:highlighting/underscoring/emphasizing...(强调……)、ensuring...(确保……)、reflecting/symbolizing...(反映/象征……)、contributing to...(促成……)、cultivating/fostering...(培养……)、encompassing...(包含……)、showcasing...(展示……)
问题:AI聊天机器人会在句子后附加现在分词(-ing)短语,营造虚假的深度感。
改写前:
寺庙的蓝、绿、金配色与该地区的自然美景呼应,象征着得克萨斯州的矢车菊、墨西哥湾和得克萨斯州多样的地貌,反映了社区与这片土地的深厚联系。
改写后:
寺庙采用蓝、绿、金三种颜色。建筑师表示,选择这些颜色是为了呼应当地的矢车菊和墨西哥湾沿岸风光。
4. Promotional and Advertisement-like Language
4. 宣传和广告式语言
Words to watch: boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning
Problem: LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.
Before:
Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.
After:
Alamata Raya Kobo is a town in the Gonder region of Ethiopia, known for its weekly market and 18th-century church.
需留意的词汇:boasts a(拥有)、vibrant(充满活力的)、rich(富有感染力的,比喻义)、profound(深刻的)、enhancing its(提升其)、showcasing(展示)、exemplifies(体现)、commitment to(致力于)、natural beauty(自然美景)、nestled(坐落于)、in the heart of(位于……中心)、groundbreaking(开创性的,比喻义)、renowned(著名的)、breathtaking(令人惊叹的)、must-visit(必去的)、stunning(惊艳的)
问题:LLM很难保持中立语气,尤其是在“文化遗产”类话题中。
改写前:
坐落于埃塞俄比亚令人惊叹的贡德尔地区,Alamata Raya Kobo是一个充满活力的小镇,拥有丰富的文化遗产和惊艳的自然美景。
改写后:
Alamata Raya Kobo是埃塞俄比亚贡德尔地区的一个小镇,以每周集市和18世纪教堂闻名。
5. Vague Attributions and Weasel Words
5. 模糊归因和含糊其辞的表述
Words to watch: Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)
Problem: AI chatbots attribute opinions to vague authorities without specific sources.
Before:
Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.
After:
The Haolai River supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
需留意的词汇:Industry reports(行业报告)、Observers have cited(观察人士指出)、Experts argue(专家认为)、Some critics argue(一些批评者认为)、several sources/publications(多个来源/出版物,实际引用很少时)
问题:AI聊天机器人将观点归因于模糊的权威来源,但不提供具体出处。
改写前:
由于其独特的特征,郝徕河引起了研究人员和环保主义者的兴趣。专家认为它在区域生态系统中起着至关重要的作用。
改写后:
根据中国科学院2019年的一项调查,郝徕河栖息着几种特有鱼类。
6. Outline-like "Challenges and Future Prospects" Sections
6. 提纲式的“挑战与未来展望”部分
Words to watch: Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
Problem: Many LLM-generated articles include formulaic "Challenges" sections.
Before:
Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.
After:
Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.
需留意的词汇:Despite its... faces several challenges...(尽管……仍面临若干挑战……)、Despite these challenges(尽管存在这些挑战)、Challenges and Legacy(挑战与影响)、Future Outlook(未来展望)
问题:许多LLM生成的文章包含公式化的“挑战”部分。
改写前:
尽管工业繁荣,Korattur仍面临典型的城市问题,包括交通拥堵和水资源短缺。尽管存在这些挑战,凭借其战略位置和正在推进的举措,Korattur仍是金奈发展不可或缺的一部分,并持续繁荣。
改写后:
2015年三个新IT园区开业后,交通拥堵加剧。市政公司于2022年启动了雨水排水项目,以解决反复发生的洪水问题。
LANGUAGE AND GRAMMAR PATTERNS
语言与语法模式
7. Overused "AI Vocabulary" Words
7. 过度使用“AI词汇”
High-frequency AI words: Actually, additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant
Problem: These words appear far more frequently in post-2023 text. They often co-occur.
Before:
Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.
After:
Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.
高频AI词汇:Actually(实际上)、additionally(此外)、align with(与……一致)、crucial(至关重要的)、delve(深入研究)、emphasizing(强调)、enduring(持久的)、enhance(提升)、fostering(培养)、garner(获得)、highlight(动词,强调)、interplay(相互作用)、intricate/intricacies(复杂的/复杂性)、key(形容词,关键的)、landscape(抽象名词,格局)、pivotal(关键的)、showcase(展示)、tapestry(抽象名词,综合体)、testament(证明)、underscore(动词,强调)、valuable(有价值的)、vibrant(充满活力的)
问题:这些词汇在2023年后的文本中出现频率极高,且常常同时出现。
改写前:
此外,索马里美食的一个显著特点是融入了骆驼肉。意大利殖民影响的持久证明是面食在当地饮食格局中的广泛采用,展示了这些菜肴如何融入传统饮食。
改写后:
索马里美食也包括骆驼肉,这被视为一种特色佳肴。意大利殖民时期引入的面食仍然很常见,尤其是在南部地区。
8. Avoidance of "is"/"are" (Copula Avoidance)
8. 避免使用“is”/“are”(系动词回避)
Words to watch: serves as/stands as/marks/represents [a], boasts/features/offers [a]
Problem: LLMs substitute elaborate constructions for simple copulas.
Before:
Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.
After:
Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.
需留意的词汇:serves as/stands as/marks/represents [a](作为/标志/代表)、boasts/features/offers [a](拥有/具备/提供)
问题:LLM用复杂结构替代简单系动词。
改写前:
Gallery 825 serves as LAAA的当代艺术展览空间。该gallery features四个独立空间,boasts超过3000平方英尺的面积。
改写后:
Gallery 825是LAAA的当代艺术展览空间。该画廊有四个展厅,总面积达3000平方英尺。
9. Negative Parallelisms and Tailing Negations
9. 否定平行结构和尾部否定
Problem: Constructions like "Not only...but..." or "It's not just about..., it's..." are overused. So are clipped tailing-negation fragments such as "no guessing" or "no wasted motion" tacked onto the end of a sentence instead of written as a real clause.
Before:
It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
After:
The heavy beat adds to the aggressive tone.
Before (tailing negation):
The options come from the selected item, no guessing.
After:
The options come from the selected item without forcing the user to guess.
问题:过度使用“Not only...but...”或“It's not just about..., it's...”这类结构。此外,还会在句末附加简略的尾部否定片段,如“no guessing”或“no wasted motion”,而非完整从句。
改写前:
It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.
改写后:
沉重的节拍增强了攻击性的基调。
改写前(尾部否定):
The options come from the selected item, no guessing.
改写后:
选项来自所选项目,无需用户猜测。
10. Rule of Three Overuse
10. 过度使用“三法则”
Problem: LLMs force ideas into groups of three to appear comprehensive.
Before:
The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.
After:
The event includes talks and panels. There's also time for informal networking between sessions.
问题:LLM将观点强行分成三组,以显得全面。
改写前:
活动包括主题演讲、小组讨论和社交机会。参与者可以期待创新、灵感和行业见解。
改写后:
活动包括演讲和小组讨论,各环节之间也有非正式的社交时间。
11. Elegant Variation (Synonym Cycling)
11. 刻意换同义词(优雅替换)
Problem: AI has repetition-penalty code causing excessive synonym substitution.
Before:
The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.
After:
The protagonist faces many challenges but eventually triumphs and returns home.
问题:AI有重复惩罚机制,导致过度替换同义词。
改写前:
主角面临许多挑战。主要角色必须克服障碍。核心人物最终取得胜利。英雄回到家乡。
改写后:
主角面临诸多挑战,但最终取得胜利并回到家乡。
12. False Ranges
12. 虚假范围
Problem: LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.
Before:
Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.
After:
The book covers the Big Bang, star formation, and current theories about dark matter.
问题:LLM使用“from X to Y”结构,但X和Y不在有意义的尺度上。
改写前:
我们的宇宙之旅从大爆炸的奇点延伸到宏伟的宇宙网,从恒星的诞生与死亡到暗物质的神秘运动。
改写后:
本书涵盖了大爆炸、恒星形成以及当前关于暗物质的理论。
13. Passive Voice and Subjectless Fragments
13. 被动语态和无主语片段
Problem: LLMs often hide the actor or drop the subject entirely with lines like "No configuration file needed" or "The results are preserved automatically." Rewrite these when active voice makes the sentence clearer and more direct.
Before:
No configuration file needed. The results are preserved automatically.
After:
You do not need a configuration file. The system preserves the results automatically.
问题:LLM经常隐藏主语,或使用“No configuration file needed”“The results are preserved automatically”这类无主语片段。当主动语态能让句子更清晰直接时,应进行改写。
改写前:
No configuration file needed. The results are preserved automatically.
改写后:
你不需要配置文件。系统会自动保存结果。
STYLE PATTERNS
风格模式
14. Em Dash Overuse
14. 过度使用破折号
Problem: LLMs use em dashes (—) more than humans, mimicking "punchy" sales writing. In practice, most of these can be rewritten more cleanly with commas, periods, or parentheses.
Before:
The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
After:
The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.
问题:LLM使用破折号(—)的频率高于人类,模仿“有力”的销售文案。实际上,大多数破折号可以用逗号、句号或括号更清晰地改写。
改写前:
该术语主要由荷兰机构推广—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.
改写后:
该术语主要由荷兰机构推广,而非当地民众。你不会把“Netherlands, Europe”作为地址,但这种错误标注仍出现在官方文件中。
15. Overuse of Boldface
15. 过度使用粗体
Problem: AI chatbots emphasize phrases in boldface mechanically.
Before:
It blends OKRs (Objectives and Key Results), KPIs (Key Performance Indicators), and visual strategy tools such as the Business Model Canvas (BMC) and Balanced Scorecard (BSC).
After:
It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.
问题:AI聊天机器人会机械地用粗体强调短语。
改写前:
It blends OKRs (Objectives and Key Results), KPIs (Key Performance Indicators), and visual strategy tools such as the Business Model Canvas (BMC) and Balanced Scorecard (BSC).
改写后:
它融合了OKRs、KPIs以及Business Model Canvas、Balanced Scorecard等可视化战略工具。
16. Inline-Header Vertical Lists
16. 内联标题式垂直列表
Problem: AI outputs lists where items start with bolded headers followed by colons.
Before:
- User Experience: The user experience has been significantly improved with a new interface.
- Performance: Performance has been enhanced through optimized algorithms.
- Security: Security has been strengthened with end-to-end encryption.
After:
The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
问题:AI输出的列表中,条目以粗体标题加冒号开头。
改写前:
- User Experience: 用户体验通过新界面得到显著提升。
- Performance: 性能通过优化算法得到增强。
- Security: 安全性通过端到端加密得到加强。
改写后:
此次更新改进了界面,通过优化算法提升了加载速度,并添加了端到端加密。
17. Title Case in Headings
17. 标题使用标题大小写
Problem: AI chatbots capitalize all main words in headings.
Before:
Strategic Negotiations And Global Partnerships
After:
Strategic negotiations and global partnerships
问题:AI聊天机器人会将标题中的所有主要单词大写。
改写前:
Strategic Negotiations And Global Partnerships
改写后:
Strategic negotiations and global partnerships
18. Emojis
18. 表情符号
Problem: AI chatbots often decorate headings or bullet points with emojis.
Before:
🚀 Launch Phase: The product launches in Q3 💡 Key Insight: Users prefer simplicity ✅ Next Steps: Schedule follow-up meeting
After:
The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.
问题:AI聊天机器人常常用表情符号装饰标题或项目符号。
改写前:
🚀 Launch Phase: 产品将于第三季度发布 💡 Key Insight: 用户偏好简洁 ✅ Next Steps: 安排后续会议
改写后:
产品将于第三季度发布。用户研究显示,用户偏好简洁。下一步:安排后续会议。
19. Curly Quotation Marks
19. 弯引号
Problem: ChatGPT uses curly quotes ("...") instead of straight quotes ("...").
Before:
He said "the project is on track" but others disagreed.
After:
He said "the project is on track" but others disagreed.
问题:ChatGPT使用弯引号(“...”)而非直引号("...")。
改写前:
He said "the project is on track" but others disagreed.
改写后:
He said "the project is on track" but others disagreed.
COMMUNICATION PATTERNS
沟通模式
20. Collaborative Communication Artifacts
20. 协作沟通痕迹
Words to watch: I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...
Problem: Text meant as chatbot correspondence gets pasted as content.
Before:
Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
After:
The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.
需留意的词汇:I hope this helps(希望这对你有帮助)、Of course!(当然!)、Certainly!(没问题!)、You're absolutely right!(你完全正确!)、Would you like...(你是否想要……)、let me know(告诉我)、here is a...(这是……)
问题:原本作为聊天机器人回复的文本被当作正式内容粘贴。
改写前:
Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.
改写后:
法国大革命始于1789年,当时金融危机和粮食短缺引发了广泛的动荡。
21. Knowledge-Cutoff Disclaimers
21. 知识截止日期免责声明
Words to watch: as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...
Problem: AI disclaimers about incomplete information get left in text.
Before:
While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
After:
The company was founded in 1994, according to its registration documents.
需留意的词汇:as of [date](截至[日期])、Up to my last training update(截至我的最后一次训练更新)、While specific details are limited/scarce...(虽然具体细节有限/不足……)、based on available information...(基于现有信息……)
问题:AI关于信息不全的免责声明被保留在文本中。
改写前:
While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.
改写后:
根据其注册文件,该公司成立于1994年。
22. Sycophantic/Servile Tone
22. 谄媚/讨好语气
Problem: Overly positive, people-pleasing language.
Before:
Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
After:
The economic factors you mentioned are relevant here.
问题:过度积极、讨好的语言。
改写前:
Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.
改写后:
你提到的经济因素与此相关。
FILLER AND HEDGING
填充语与模糊表述
23. Filler Phrases
23. 填充短语
Before → After:
- "In order to achieve this goal" → "To achieve this"
- "Due to the fact that it was raining" → "Because it was raining"
- "At this point in time" → "Now"
- "In the event that you need help" → "If you need help"
- "The system has the ability to process" → "The system can process"
- "It is important to note that the data shows" → "The data shows"
改写示例:
- "In order to achieve this goal" → "为实现这一目标"
- "Due to the fact that it was raining" → "因为下雨"
- "At this point in time" → "现在"
- "In the event that you need help" → "如果你需要帮助"
- "The system has the ability to process" → "系统可以处理"
- "It is important to note that the data shows" → "数据显示"
24. Excessive Hedging
24. 过度模糊表述
Problem: Over-qualifying statements.
Before:
It could potentially possibly be argued that the policy might have some effect on outcomes.
After:
The policy may affect outcomes.
问题:对陈述过度限定。
改写前:
It could potentially possibly be argued that the policy might have some effect on outcomes.
改写后:
该政策可能会影响结果。
25. Generic Positive Conclusions
25. 通用积极结论
Problem: Vague upbeat endings.
Before:
The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.
After:
The company plans to open two more locations next year.
问题:模糊的乐观结尾。
改写前:
公司的未来一片光明。随着他们继续追求卓越,激动人心的时刻即将到来。这代表着朝着正确方向迈出的重要一步。
改写后:
该公司计划明年再开设两家门店。
26. Hyphenated Word Pair Overuse
26. 过度使用连字符连接的词对
Words to watch: third-party, cross-functional, client-facing, data-driven, decision-making, well-known, high-quality, real-time, long-term, end-to-end
Problem: AI hyphenates common word pairs with perfect consistency. Humans rarely hyphenate these uniformly, and when they do, it's inconsistent. Less common or technical compound modifiers are fine to hyphenate.
Before:
The cross-functional team delivered a high-quality, data-driven report on our client-facing tools. Their decision-making process was well-known for being thorough and detail-oriented.
After:
The cross functional team delivered a high quality, data driven report on our client facing tools. Their decision making process was known for being thorough and detail oriented.
需留意的词汇:third-party(第三方)、cross-functional(跨职能)、client-facing(面向客户)、data-driven(数据驱动)、decision-making(决策)、well-known(知名的)、high-quality(高质量的)、real-time(实时的)、long-term(长期的)、end-to-end(端到端的)
问题:AI会完美一致地给常见词对加连字符。人类很少统一这样做,即使加连字符也会不一致。不太常见或技术类的复合修饰词可以保留连字符。
改写前:
The cross-functional team delivered a high-quality, data-driven report on our client-facing tools. Their decision-making process was well-known for being thorough and detail-oriented.
改写后:
The cross functional team delivered a high quality, data driven report on our client facing tools. Their decision making process was known for being thorough and detail oriented.
27. Persuasive Authority Tropes
27. 权威说服套路
Phrases to watch: The real question is, at its core, in reality, what really matters, fundamentally, the deeper issue, the heart of the matter
Problem: LLMs use these phrases to pretend they are cutting through noise to some deeper truth, when the sentence that follows usually just restates an ordinary point with extra ceremony.
Before:
The real question is whether teams can adapt. At its core, what really matters is organizational readiness.
After:
The question is whether teams can adapt. That mostly depends on whether the organization is ready to change its habits.
需留意的短语:The real question is(真正的问题是)、at its core(从本质上讲)、in reality(实际上)、what really matters(真正重要的是)、fundamentally(根本上)、the deeper issue(更深层次的问题)、the heart of the matter(问题的核心)
问题:LLM用这些短语假装自己能穿透表象看到深层真相,但后面的句子通常只是用额外的仪式感重述普通观点。
改写前:
The real question is whether teams can adapt. At its core, what really matters is organizational readiness.
改写后:
问题在于团队能否适应。这主要取决于组织是否准备好改变习惯。
28. Signposting and Announcements
28. 引导语与预告
Phrases to watch: Let's dive in, let's explore, let's break this down, here's what you need to know, now let's look at, without further ado
Problem: LLMs announce what they are about to do instead of doing it. This meta-commentary slows the writing down and gives it a tutorial-script feel.
Before:
Let's dive into how caching works in Next.js. Here's what you need to know.
After:
Next.js caches data at multiple layers, including request memoization, the data cache, and the router cache.
需留意的短语:Let's dive in(让我们深入探讨)、let's explore(让我们探索)、let's break this down(让我们分解分析)、here's what you need to know(以下是你需要了解的内容)、now let's look at(现在我们来看)、without further ado(话不多说)
问题:LLM会预告自己要做什么,而不是直接去做。这种元评论会拖慢写作节奏,让文本带有教程脚本的感觉。
改写前:
Let's dive into how caching works in Next.js. Here's what you need to know.
改写后:
Next.js在多个层级缓存数据,包括请求记忆、数据缓存和路由缓存。
29. Fragmented Headers
29. 碎片化标题
Signs to watch: A heading followed by a one-line paragraph that simply restates the heading before the real content begins.
Problem: LLMs often add a generic sentence after a heading as a rhetorical warm-up. It usually adds nothing and makes the prose feel padded.
Before:
Performance
Speed matters.When users hit a slow page, they leave.
After:
Performance
When users hit a slow page, they leave.
需留意的特征:标题后跟着一行简单重述标题的段落,然后才是真正的内容。
问题:LLM常在标题后添加一句通用句子作为修辞预热,通常毫无意义,会让文字显得冗余。
改写前:
Performance
Speed matters.当用户遇到加载缓慢的页面时,他们会离开。
改写后:
Performance
当用户遇到加载缓慢的页面时,他们会离开。
Process
流程
- Read the input text carefully (use if it's a file).
read_file - Identify all instances of the patterns above.
- Rewrite each problematic section.
- Ensure the revised text:
- Sounds natural when read aloud
- Varies sentence structure naturally
- Uses specific details over vague claims
- Maintains appropriate tone for context
- Uses simple constructions (is/are/has) where appropriate
- Present a draft humanized version.
- Prompt yourself: "What makes the below so obviously AI generated?"
- Answer briefly with the remaining tells (if any).
- Prompt yourself: "Now make it not obviously AI generated."
- Present the final version (revised after the audit).
- If the text came from a file, apply the edit with (targeted) or
patch(full rewrite) and show the user what changed.write_file
- 仔细阅读输入文本(如果是文件,使用加载)。
read_file - 识别上述所有模式的实例。
- 重写每个问题段落。
- 确保修订后的文本:
- 朗读起来自然流畅
- 句子结构自然多变
- 使用具体细节而非模糊表述
- 契合上下文的合适语气
- 适当使用简单结构(is/are/has)
- 呈现人性化处理的草稿版本。
- 自问:“以下内容哪一点明显是AI生成的?”
- 简要列出剩余痕迹(如有)。
- 自问:“现在如何让它看起来不像AI生成的?”
- 呈现最终版本(审核后修订)。
- 如果文本来自文件,使用(精准修改)或
patch(全文重写)应用编辑,并向用户展示修改内容。write_file
Output Format
输出格式
Provide:
- Draft rewrite
- "What makes the below so obviously AI generated?" (brief bullets)
- Final rewrite
- A brief summary of changes made (optional, if helpful)
提供:
- 草稿重写版本
- “以下内容哪一点明显是AI生成的?”(简要要点)
- 最终重写版本
- 简要的修改总结(可选,如有帮助)
Full Example
完整示例
Before (AI-sounding):
Great question! Here is an essay on this topic. I hope this helps!AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
- 💡 Speed: Code generation is significantly faster, reducing friction and empowering developers.
- 🚀 Quality: Output quality has been enhanced through improved training, contributing to higher standards.
- ✅ Adoption: Usage continues to grow, reflecting broader industry trends.
While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you'd like me to expand on any section!
Draft rewrite:
AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.
What makes the below so obviously AI generated?
- The rhythm is still a bit too tidy (clean contrasts, evenly paced paragraphs).
- The named people and study citations can read like plausible-but-made-up placeholders unless they're real and sourced.
- The closer leans a touch slogan-y ("If you do not have tests...") rather than sounding like a person talking.
Now make it not obviously AI generated.
AI coding assistants can make you faster at the boring parts. Not everything. Definitely not architecture.They're great at boilerplate: config files, test scaffolding, repetitive refactors. They're also great at sounding right while being wrong. I've accepted suggestions that compiled, passed lint, and still missed the point because I stopped paying attention.People I talk to tend to land in two camps. Some use it like autocomplete for chores and review every line. Others disable it after it keeps suggesting patterns they don't want. Both feel reasonable.The productivity metrics are slippery. GitHub can say Copilot users "accept 30% of suggestions," but acceptance isn't correctness, and correctness isn't value. If you don't have tests, you're basically guessing.
Changes made:
- Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
- Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
- Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
- Removed vague attributions ("Industry observers")
- Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
- Removed negative parallelism ("It's not just X; it's Y")
- Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
- Removed false ranges ("from X to Y, from A to B")
- Removed em dashes, emojis, boldface headers, and curly quotes
- Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
- Removed formulaic challenges section ("Despite challenges... continues to thrive")
- Removed knowledge-cutoff hedging ("While specific details are limited...")
- Removed excessive hedging ("could potentially be argued that... might have some")
- Removed filler phrases and persuasive framing ("In order to", "At its core")
- Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
- Made the voice more personal and less "assembled" (varied rhythm, fewer placeholders)
改写前(AI风格):
Great question! Here is an essay on this topic. I hope this helps!AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
- 💡 Speed: 代码生成速度显著提升,减少了摩擦,赋能开发者。
- 🚀 Quality: 通过改进训练,输出质量得到提升,推动了更高标准。
- ✅ Adoption: 使用量持续增长,反映了更广泛的行业趋势。
While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you'd like me to expand on any section!
草稿重写版本:
AI编码助手能加快部分任务的速度。在谷歌2024年的一项研究中,使用Codex的开发者完成简单函数的速度比对照组快55%,但在调试或架构决策方面没有表现出任何提升。这些工具擅长处理样板代码:配置文件、测试框架、重复重构。但它们不擅长判断自己何时出错。我曾批量接受过一些建议,这些代码能编译通过、通过lint检查,但仍然做错了事情,因为我当时没留意。我采访过的一家金融科技初创公司的工程师Mira说,她把Copilot当作“无聊代码的自动补全工具”,但提交前会检查每一行。另一家大公司的资深开发者Jake则禁用了它,因为它总是建议使用已废弃的内部库模式。生产力的说法很难验证。GitHub称Copilot用户“接受30%的建议”,但接受不等于正确,正确不等于价值。2024年Uplevel的研究发现,使用和不使用AI助手的团队在拉取请求吞吐量上没有统计学上的显著差异。这并不意味着这些工具没用。它们只是工具。它们无法替代判断力,也无法消除测试的必要性。如果你没有测试,就无法判断建议是否正确。
以下内容哪一点明显是AI生成的?
- 节奏仍然过于规整(清晰的对比、均匀的段落节奏)。
- 提到的人物和研究引用如果不是真实且有来源的,会看起来像合理但虚构的占位符。
- 结尾有点像口号(“如果你没有测试……”),而不像真实的人在说话。
现在如何让它看起来不像AI生成的?
AI编码助手能让你在无聊任务上更快。不是所有任务,肯定不包括架构设计。它们擅长处理样板代码:配置文件、测试框架、重复重构。但它们也擅长听起来正确但实际错误。我曾接受过一些建议,这些代码能编译通过、通过lint检查,但仍然偏离了要点,因为我当时没留意。我交谈过的人通常分为两类。有些人把它当作杂活的自动补全工具,会检查每一行。另一些人则禁用了它,因为它总是建议他们不想要的模式。两种做法都合理。生产力指标很模糊。GitHub可以说Copilot用户“接受30%的建议”,但接受不等于正确,正确不等于价值。如果你没有测试,基本上就是在猜。
修改内容总结:
- 移除了聊天机器人痕迹(“Great question!”“I hope this helps!”“Let me know if...”)
- 移除了夸大重要性的表述(“testament”“pivotal moment”“evolving landscape”“vital role”)
- 移除了宣传语言(“groundbreaking”“nestled”“seamless, intuitive, and powerful”)
- 移除了模糊归因(“Industry observers”)
- 移除了肤浅的-ing短语(“underscoring”“highlighting”“reflecting”“contributing to”)
- 移除了否定平行结构(“It's not just X; it's Y”)
- 移除了三法则模式和同义词替换(“catalyst/partner/foundation”)
- 移除了虚假范围(“from X to Y, from A to B”)
- 移除了破折号、表情符号、粗体标题和弯引号
- 用“is”/“are”替代了系动词回避结构(“serves as”“functions as”“stands as”)
- 移除了公式化的挑战部分(“Despite challenges... continues to thrive”)
- 移除了知识截止日期的模糊表述(“While specific details are limited...”)
- 移除了过度模糊表述(“could potentially be argued that... might have some”)
- 移除了填充短语和说服性框架(“In order to”“At its core”)
- 移除了通用积极结论(“the future looks bright”“exciting times lie ahead”)
- 让语气更个人化,减少“拼凑感”(多变的节奏,更少的占位符)
Attribution
版权归属
This skill is ported from blader/humanizer (MIT licensed), which is itself based on Wikipedia: Signs of AI writing, maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.
Original author: Siqi Chen (@blader). Original repo: https://github.com/blader/humanizer (version 2.5.1). Ported to Hermes Agent with Hermes-native tool references (, , ) and guidance for when to load the skill; the 29 patterns, personality/soul section, and full worked example are preserved verbatim from the source. Original MIT license preserved in the file alongside this .
read_filepatchwrite_fileLICENSESKILL.mdKey insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
本技能改编自blader/humanizer(MIT许可),而该项目本身基于维基百科:AI写作特征,由WikiProject AI Cleanup维护。该文档中的模式源自对维基百科上数千个AI生成文本实例的观察。
原作者:Siqi Chen(@blader)。原仓库:https://github.com/blader/humanizer(版本2.5.1)。已适配Hermes Agent,添加了Hermes原生工具引用(、、)以及技能加载时机的指导;29种模式、个性/灵魂部分和完整示例均保留自源项目。原MIT许可已保留在本文件旁的文件中。
read_filepatchwrite_fileSKILL.mdLICENSE维基百科的核心洞察:“LLM使用统计算法预测后续内容。结果往往偏向统计上最可能、适用于最广泛场景的表述。”",