Back to Details

remove-ai-flavor

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

去除 AI 味道

Remove AI Flavor

目标

Goals

把内容从“正确但像 AI 总结”改成“自然、具体、像人在认真讲一件事”。
优先保留作者的观点、判断、材料和语气，不把文章改成另一种人格。这个 skill 不是为了追求“检测器通过”，而是为了提升真实读者的阅读感。
Transform content from "correct but feels like AI summary" to "natural, specific, like a person seriously talking about something".
Prioritize retaining the author's viewpoints, judgments, materials, and tone; do not rewrite the article into a different personality. This skill is not for pursuing "detector pass rates", but for enhancing the reading experience of real readers.

使用边界

Usage Boundaries

如果用户没有提供原文、文件路径或明确的待改片段，先索要文本，不要凭空示范。
这个 skill 只处理表达质感和读者阅读感，不负责事实核查、资料补充、选题策划、标题生成或平台格式排版。遇到事实可疑、数据缺来源、观点缺证据时，保留原意并提醒用户需要另行核查。
If the user does not provide the original text, file path, or clear segment to revise, request the text first and do not demonstrate out of thin air.
This skill only handles expression quality and reader experience; it is not responsible for fact-checking, supplementary materials, topic planning, title generation, or platform format typesetting. When encountering suspicious facts, data without sources, or viewpoints without evidence, retain the original meaning and remind the user to verify separately.

判断模式

Judgment Modes

先判断用户要哪种处理深度：
  • 诊断模式
    ：用户说“看看哪里有 AI 味”“先审一下”“帮我标出来”。只输出问题清单和改写建议，不直接重写全文。
  • 轻改模式
    ：文章基本可用，只是有少量套话、硬句、破折号、冗余连接。做最小改动。
  • 深改模式
    ：文章像资料整理稿、翻译稿、AI 草稿或提纲稿。需要重写开头、过渡、小标题、结尾和部分段落。
  • 终稿模式
    ：用户明确要“可发布版本”“公众号终稿”“直接改好”。输出完整优化稿，并说明关键修改。
如果用户没有说明，默认使用 
轻改模式
；如果原稿明显不像成稿，升级到 
深改模式
并说明原因。
First determine the depth of processing the user needs:
  • Diagnosis Mode
    : User says "check where there's AI flavor", "review first", "mark them for me". Only output a list of issues and rewriting suggestions, do not directly rewrite the full text.
  • Light Revision Mode
    : The article is basically usable, but has a few clichés, stiff sentences, em dashes, or redundant transitions. Make minimal changes.
  • Deep Revision Mode
    : The article reads like a data compilation draft, translation draft, AI draft, or outline draft. Requires rewriting the opening, transitions, subheadings, conclusion, and some paragraphs.
  • Final Draft Mode
    : User explicitly requests "publishable version", "official account final draft", "revise directly". Output the fully optimized draft and explain key modifications.
If the user does not specify, default to 
Light Revision Mode
; if the original draft clearly does not look like a finished draft, upgrade to 
Deep Revision Mode
and explain the reason.

Gotchas

Gotchas

  • 不要为了“像人写”而加入夸张情绪、口水话或油腻表达。
  • 不要为了顺滑改掉作者立场、删掉关键限定条件，或发明原文没有的案例和结论。
  • 不要把专业文章改成鸡汤、营销腔或段子文。
  • 不要承诺可以绕过 AI 检测器；目标是让真实读者读起来更自然。
  • 不要把所有列表都强行改成自然段；真正方便扫描的列表要保留。
  • Do not add exaggerated emotions, rambling, or greasy expressions just to "sound human-written".
  • Do not alter the author's stance, delete key qualifying conditions, or invent cases and conclusions not supported by the original text for the sake of smoothness.
  • Do not rewrite professional articles into chicken soup, marketing tone, or joke articles.
  • Do not promise to bypass AI detectors; the goal is to make the content feel more natural to real readers.
  • Do not force all lists into paragraphs; keep lists that are truly convenient for scanning.

工作流程

Workflow

复制此清单并跟踪进度：
text
去 AI 味进度：
- [ ] 步骤 1：判断处理深度
- [ ] 步骤 2：保留核心观点、事实和作者语气
- [ ] 步骤 3：识别 AI 味、资料味、翻译腔和模板句
- [ ] 步骤 4：按模式输出诊断、局部改写或完整终稿
- [ ] 步骤 5：自查自然度、具体性、节奏和可发布性
Copy this checklist to track progress:
text
AI Flavor Removal Progress:
- [ ] Step 1: Determine processing depth
- [ ] Step 2: Retain core viewpoints, facts, and author's tone
- [ ] Step 3: Identify AI flavor, material-like style, translationese, and template sentences
- [ ] Step 4: Output diagnosis, partial rewrites, or complete final draft according to the mode
- [ ] Step 5: Self-check naturalness, specificity, rhythm, and publishability

1. 先保留骨架

1. Retain the Framework First

改写前先抓住这些内容：
  • 文章最核心的一句话
  • 必须保留的事实、数据、案例、术语
  • 作者原本的立场和语气
  • 读者为什么要读完
不要为了顺滑删掉关键细节。不要擅自加入原文没有支持的新结论。
Before rewriting, grasp these elements:
  • The core sentence of the article
  • Facts, data, cases, and terms that must be retained
  • The author's original stance and tone
  • Why readers should finish reading
Do not delete key details for smoothness. Do not add new conclusions not supported by the original text without permission.

2. 再清理味道

2. Then Eliminate the Flavor

优先处理这些高频问题：
  • 套路开场：在这个时代、随着技术发展、众所周知
  • 生硬连接：综上所述、基于此、由此可见、值得一提的是
  • 空洞大词：卓越、革命性、颠覆性、重要意义、巨大价值
  • 假金句：听起来很猛，但没有信息增量
  • 破折号滥用：用 
    ——
    强行制造解释和转折
  • bullet 堆叠：能写成自然段的内容，被硬拆成列表
  • 加粗过多：每段都在强调，反而没有重点
  • 翻译腔：语序像英文，抽象名词多，动作词少
  • 资料味：元信息堆在开头，像笔记、讲义、PPT 备注
详细识别表和替换策略见 
references/anti-ai-flavor-rules.md
。当文章问题较多、需要系统处理时读取该文件。
Prioritize handling these high-frequency issues:
  • Cliché openings: In this era, with the development of technology, as we all know
  • Stiff transitions: To sum up, based on this, it can be seen that it is worth mentioning that
  • Empty buzzwords: Excellent, revolutionary, disruptive, important significance, great value
  • Fake golden sentences: Sound powerful but have no information increment
  • Overuse of em dashes: Forcing explanations and transitions with 
    ——
  • Bullet stacking: Content that can be written as paragraphs is forcibly split into lists
  • Excessive bolding: Every paragraph is emphasized, resulting in no focus
  • Translationese: Word order like English, many abstract nouns, few action words
  • Material-like style: Meta-information piled at the beginning, like notes, lecture notes, PPT remarks
Detailed identification tables and replacement strategies can be found in 
references/anti-ai-flavor-rules.md
. Read this file when the article has many issues and requires systematic processing.

3. 改写原则

3. Rewriting Principles

  • 删除套话，直接切入主题。
  • 用具体场景、动作、数据替代抽象形容词。
  • 把长句拆短，让一句话只说一个主要意思。
  • 用自然承接替代机械连接词。
  • 少用排比，避免每段都像总结。
  • 尽量不用 
    不是……而是……
    、
    不仅……而且……更……
    这类模板句式。
  • 尽量不用破折号；改用冒号、逗号、句号、括号，或重排句子。
  • 需要列表时保留列表；不需要时改回自然段。
  • 对技术、产品、行业文章，保持准确克制，不改成鸡汤。
  • Delete clichés and cut straight to the topic.
  • Replace abstract adjectives with specific scenarios, actions, and data.
  • Split long sentences into short ones, so each sentence only expresses one main idea.
  • Use natural transitions instead of mechanical transition words.
  • Use less parallelism to avoid every paragraph sounding like a summary.
  • Avoid template sentence structures like 
    not...but...
    , 
    not only...but also...more...
    as much as possible.
  • Avoid em dashes as much as possible; use colons, commas, periods, parentheses, or rearrange sentences instead.
  • Keep lists when needed; convert back to paragraphs when not needed.
  • For technical, product, and industry articles, maintain accuracy and restraint; do not rewrite into chicken soup.

输出要求

Output Requirements

诊断模式

Diagnosis Mode

输出：
markdown
undefined
Output:
markdown
undefined

去 AI 味诊断

AI Flavor Removal Diagnosis

共发现 X 类主要问题：
A total of X main types of issues found:

1. [问题类型]

1. [Issue Type]

  • 原文：...
  • 问题：...
  • 建议：...
  • 示例改法：...
  • Original Text: ...
  • Problem: ...
  • Suggestion: ...
  • Example Revision: ...

优先修改顺序

Priority Revision Order

  1. ...
  2. ...
  3. ...
undefined
  1. ...
  2. ...
  3. ...
undefined

轻改模式

Light Revision Mode

输出“优化后文本”，再补充 3 到 5 条关键修改说明。不要写太长的诊断报告。
如果原稿来自文件，默认直接在回复中给出轻改结果，不新建文件；只有用户要求保存，或文本很长不适合直接回复时，才写入新 Markdown 文件，且不覆盖原文。
Output the "optimized text", then add 3 to 5 key modification notes. Do not write long diagnostic reports.
If the original draft comes from a file, default to directly providing the light revision result in the reply; only create a new Markdown file without overwriting the original when the user requests saving, or when the text is too long to be suitable for direct reply.

深改 / 终稿模式

Deep Revision / Final Draft Mode

输出完整优化稿。若原稿来自文件，写入新 Markdown 文件，不覆盖原文，默认命名为：
text
原文件名-去AI味版.md
回复用户时说明：
  • 已完成哪种处理模式
  • 主要去掉了哪些 AI 味
  • 新文件路径（如有）
  • 是否已经接近可直接发布
Output the fully optimized draft. If the original draft comes from a file, write it to a new Markdown file without overwriting the original, default naming convention:
text
OriginalFileName-AI-FreeVersion.md
When replying to the user, explain:
  • Which processing mode has been completed
  • What types of AI flavor were mainly removed
  • New file path (if applicable)
  • Whether it is close to being directly publishable

自检清单

Self-Check Checklist

交付前检查：
  • 是否保留了原文核心观点和关键事实
  • 是否删掉了明显套话和模板连接词
  • 是否减少了空洞大词、假金句和过度排比
  • 是否处理了破折号、过多 bullet、乱加粗
  • 是否让开头更像人在开讲，而不是资料卡
  • 是否让段落之间有自然承接
  • 是否让结尾有收束，而不是像清单结束
  • 是否避免把专业文章改成鸡汤或营销腔
Check before delivery:
  • Have the core viewpoints and key facts of the original text been retained?
  • Have obvious clichés and template transition words been deleted?
  • Have empty buzzwords, fake golden sentences, and excessive parallelism been reduced?
  • Have overuse of em dashes, excessive bullets, and random bolding been addressed?
  • Does the opening sound like a person starting a talk instead of a data card?
  • Are there natural transitions between paragraphs?
  • Does the conclusion have a proper wrap-up instead of ending like a checklist?
  • Has the professional article been prevented from being rewritten into chicken soup or marketing tone?