AI Agent Hub
Back to skills
De-AI-ify Text Refinement icon

De-AI-ify Text Refinement

Content Creation Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @user_7e25a48a/thisifsa according to https://skillhub.cn/install/skillhub.md.

About this skill

What it fixes

AI-generated technical writing is often structurally clean but too smooth, overly certain, and over-packaged. This skill polishes that “AI flavor” without rewriting the argument or adding new claims. It focuses on wording, syntax, tone, and rhetoric so the text reads more like a real engineer or author.

How it works

It runs detection, rewriting, and verification. Detection targets patterns such as absolute statements, unsupported numbers, flowery metaphors, formulaic summaries, repeated three-item parallelism, excessive emoji, dash-plus-snark, and “not X, but Y” framing. Rewriting stays at the surface: headings, lists, bold text, tables, and information density are preserved. For example, “300% efficiency gains” may become a more cautious phrasing, and abstract “cognitive upgrade logic” becomes a concrete explanation. Verification checks meaning preservation, length inflation, structural flattening, and whether the output becomes a new template.

Boundaries

It is useful for cleaning machine-like prose in existing articles, blog posts, docs, or release notes. It is not for drafting from scratch, adding facts, inventing case studies, or expanding short notes into long-form content. It preserves register, keeps technical writing technical, avoids converting fullwidth and halfwidth punctuation, and does not introduce unsupported conclusions. If the source relies on fabricated data or anonymous anecdotes, it tends to remove them rather than keep them.

Use Cases

  • Before publishing, clean up “not X, but Y” phrasing, parallelism, and inflated numbers in a technical blog post.
  • Polish AI-generated product notes into an engineer's voice while keeping headings, lists, and bold text.
  • Reduce emoji overload and dash-plus-snark in release copy without changing the original information or tone.
  • Review a draft doc and remove unsupported anecdotes or fabricated data instead of adding new claims.

Best For

  • Engineers who draft technical blogs with AI and need to remove template-like phrasing before publishing.
  • Developers maintaining product notes or technical docs who want more natural wording.
  • Technical writers polishing AI drafts so they read like a real author.
  • Content editors reviewing docs and removing unsupported data or fabricated anecdotes.