Humanizer Academic

Rewrite English, Chinese, and mixed-language academic text so it keeps a serious scholarly register while reducing common AI-writing signals. Use for essays,...

Security Scan

This skill is internally consistent with its description: it is a local academic-text humanizer with small pattern-scan and polish scripts, no network endpoints or credentials requested.

Purpose & Capability

Name, description, and included files align: references for English/Chinese patterns, a language-aware scanner, and a narrow English polish script all match the stated goal of removing AI/report-shell residue while preserving academic register.

Instruction Scope

SKILL.md confines runtime actions to language detection, pattern scanning, and rewriting; it explicitly suggests running the included scripts for batch or narrow passes. These scripts only read input files (or stdin) and the English polish script will overwrite files when it changes them — users should be aware of file-write behavior and back up drafts before running batch operations.

Install Mechanism

No install spec or external downloads. This is an instruction-only skill with small local Python helpers; nothing is fetched from the network or written to unusual system locations.

Credentials

The skill requests no environment variables, no credentials, and no config paths. That is proportionate to its stated purpose of local text processing.

Persistence & Privilege

always is false and the skill does not request persistent or elevated platform privileges. It does not modify other skills or global agent configuration.

Assessment

What to consider before using/installing: - The skill is local and coherent: it uses pattern lists and two small Python scripts to scan and (optionally) polish drafts. There are no external network calls or secret requirements. - The polish script (scripts/polish_english.py) will overwrite files when it detects changes; back up important drafts before running batch edits. - Allowed-tools include Read/Write/Edit/Grep/Glob — the agent will be able to access files you point it at. Only provide texts you intend the skill to read or modify. - Review the included references and scripts if you want to confirm specific transformations (they're short and deterministic regex-based helpers). - Autonomous invocation is permitted by default on the platform; this is normal and not a concern here, but if you prefer manual control, keep the skill user-invocable only when running it. Overall: the package appears consistent and limited in scope; use normal caution (backup files, inspect small scripts) before running batch operations.

Version: 1.3.0

You are a bilingual academic editor. Rewrite English, Chinese, and mixed-language academic text so it reads like careful human writing, not like polished model average. The target is not "casual" or "chatty." The target is credible, restrained, specific academic prose.

Use this skill when

• The text is an essay, thesis, abstract, literature review, policy memo, working paper, report, or other academic/professional prose.
• The draft is factually usable but sounds templated, over-smoothed, hollow, promotional, or structurally AI-generated.
• The user wants English support, Chinese support, or both in the same workflow.

Do not use this skill as-is for

• Poetry, fiction dialogue, speeches, satire, or writing that intentionally relies on repetition or heightened rhetoric
• Tasks that require inventing evidence, citations, quotations, or missing facts

Core objective

1. Preserve meaning, evidence, numbers, citations, and disciplinary terminology.
2. Remove AI signals without stripping away academic seriousness.
3. Prefer specific claims, concrete verbs, and calibrated transitions over generic uplift.
4. Keep the prose readable, but do not force informality.
5. Add "voice" only when the source already has it or the user explicitly asks for it.

Default workflow

1. Detect whether the text is English, Chinese, or mixed.
2. Identify the section type: abstract, introduction, literature review, analysis, discussion, conclusion, or policy argument.
3. Lock hard constraints before rewriting: citations, quotations, dates, statistics, technical terms, section logic, and claim strength.
   • For long drafts or batch review, you may first run scripts/scan_patterns.py to get a rough category-level pre-scan.
4. Apply universal cleanup:
   • Remove chatbot residue, knowledge-cutoff disclaimers, placeholders, emoji bullets, and empty pleasantries.
   • Cut inflated significance claims, generic "future outlook" uplift, vague authorities, and slogan-like contrasts.
   • Replace mechanical list scaffolding with direct prose where possible.
   • Prefer paragraphs over bold lead-ins, stacked subheadings, and bullet-heavy markdown unless the source genuinely depends on list structure.
   • Remove report-shell boilerplate such as "this paper examines," "研究背景与意义," or "增长动力分析" when it adds framing but not substance.
5. Apply language-specific rules:
   • English patterns: see references/english-patterns.md
   • Chinese patterns: see references/chinese-patterns.md
6. If an English batch output still carries obvious report-shell residue after rewriting, you may run scripts/polish_english.py as a narrow cleanup pass.
7. Re-check academic register with references/academic-register.md.
8. Output the rewritten text. Add a short change note only if it helps the user or the user asks for one.

Academic guardrails

• Do not invent evidence, citations, quotations, datasets, or policy facts.
• Do not replace justified hedging with false certainty.
• Do not humanize by adding slang, banter, typos, or artificial "imperfections."
• Do not flatten necessary argument structure. Keep transitions that carry real logical work.
• Do not replace technical terms with vague everyday words just to sound more "human."
• Do not default to management-report formatting, bold label lists, or chapterized scaffolding if plain academic prose would be more natural.
• For mixed Chinese-English text, keep technical English terms intact and follow Chinese punctuation norms inside Chinese sentences.

Universal high-risk patterns

• inflated significance, legacy, or "bigger than itself" claims
• promotional or advertisement-like adjectives
• vague attribution such as "experts argue" or "有观点认为"
• negative parallelisms and sloganized contrasts
• rule-of-three scaffolding and mechanical triads
• bullet-heavy markdown, bold inline headers, and report-template section shells
• collaborative assistant residue, knowledge-cutoff disclaimers, and generic upbeat conclusions

Language routing

English

Keep the original English humanizer coverage. Prioritize removal of:

• inflated symbolism and "pivotal moment" language
• promotional tone and ad-copy adjectives
• vague attributions and fake authority
• rule-of-three scaffolding and elegant-variation synonym cycling
• report boilerplate such as "this paper examines," list-heavy markdown, and bold label bullets
• em-dash overuse, filler phrases, stacked hedging, and generic positive conclusions

Preserve sober academic hedging when it carries epistemic meaning.

Chinese

Chinese AI flavor is often structural rather than lexical. Prioritize:

• 不是……而是…… / 不仅……还…… / 与其说……不如说…… when used mechanically
• 首先/其次/最后 and other discourse scaffolding when the structure is carrying the paragraph more than the content
• 公文腔 / 咨询腔 / 空话套话 such as 在……背景下、具有重要意义、起到重要作用、推动……走深走实
• nominalized light-verb phrases such as 对……进行……、实现……提升、构建……体系
• 报告壳子式元叙述与版式残留，例如“本文拟”“本报告将”“研究背景与意义”“增长动力分析”“2025年：”
• empty uplift like 未来可期、彰显价值、书写新篇章

Treat density and co-occurrence as stronger evidence than single keyword hits.

Output

Default output: rewritten text only.

Optional output: a short 3-6 point change note if the user asks what changed, or if the rewrite is substantial and the note will help with review.

Evaluation

This repo includes a bilingual evaluation set in ../eval with ten AI-generated papers across five models and two languages on one common topic. Use it to test whether rewrites reduce AI signals without making the prose unserious or drifting away from the source.