AI Agent Hub
Back to skills
AI Flavor Remover icon

AI Flavor Remover

Content Creation Updated 2026.08.30

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

Please follow https://skillhub.cn/install/skillhub.md to install @user_858115ff/ai-flavor-clear.

About this skill

Problem

AI-generated drafts often sound overly smooth: neat parallelism, uniform sentence length, and mechanical transitions can trigger high AIGC suspicion in tools such as Zhuque, GPTZero, and similar detectors. Simply deleting “AI words” is unreliable because detectors weigh statistical signals like perplexity, burstiness, topic consistency, and word-frequency distribution. This skill reframes the task from removing AI flavor to injecting human signals: concrete names, dates, numbers, colloquial voice, uncertainty, digressions, and fragments.

How It Works

The package centers on scripts/detect.py, scripts/rewrite.py, and references/style-guide.md. detect.py returns a 0-100 human-signal score plus six sub-scores for specificity, burstiness, doubt, digression, voice, and imperfection. rewrite.py performs a conservative surface pass, removing dead filler, mechanical connectors, and double em dashes without deleting substance. The workflow is to score the draft, identify missing human signals, run the light cleanup, rewrite semantically using the style guide, re-score, and then verify on the detector’s official site. For education writing, it preserves required domain terms such as “立德树人” and “核心素养” while rewriting the surrounding formulaic phrasing.

Limits and Notes

The built-in score is not a Zhuque proxy and does not guarantee passing AIGC checks. Detectors keep changing, and official sites remain authoritative. If a result stays high, continue adding specificity, conversational texture, and imperfect syntax rather than relying on synonym swaps alone.

Use Cases

  • Rewrite a teaching summary with concrete classroom details before Zhuque submission.
  • Score a product draft for human signals and add missing voice, doubt, and specifics.
  • Turn an AI-drafted postmortem into fragmented, digressive, self-doubting prose for detector tests.
  • Clean mechanical connectors in an abstract and add years, counts, and uncertainty before review.

Best For

  • Classroom teachers submitting teaching case studies to Zhuque who need to keep terms like core literacy while removing AI-sounding boilerplate.
  • Graduate students submitting abstracts to CNKI AIGC who want to reduce template-like phrasing in the intro.
  • Product managers reviewing model-drafted release notes who need concrete version numbers and usage scenarios.
  • English editors submitting copy to GPTZero who want professional terms plus colloquial uncertainty.