awesome-humanize-en

Solid

Use when: the user asks you to check, rewrite, humanize, or de-slop English text that shows signs of AI generation (ChatGPT, Claude, Gemini, Grok, DeepSeek, GPT-5, Qwen, Llama, any LLM). Trigger for requests like: 'humanize this', 'make it sound human / natural', 'remove the AI voice', 'this reads like a chatbot', 'AI detector for English', 'check for AI', 'de-slop', 'reduce AI-isms', remove clichés / filler / corporate jargon / emoji bullet lists 🚀 / gratuitous em-dashes / sycophantic tone / fabricated sources. Also when visible copy-paste chatbot markers are present: `:contentReference`, `?utm_source=chatgpt.com`, `oai_citation`, `grok_card://`, `vertexaisearch`, `turn0search`, `[cite_start]`, `[cite: 8]`. Do NOT use: text that is not in English, source code / scripts (even about NLP), legal documents (officialese is the genre), literary prose / poetry / résumés (there the em-dash, rhythm and compression are an authorial device).

AI & Automation 2 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
16
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Humanize English text A skill for editing English text that carries traces of AI generation. The goal is to make the text read naturally without distorting its meaning. It draws on the Wikipedia AI Cleanup project and its "Signs of AI writing" guidance. ## When to use - English text reads as mechanical, flat, or templated. - You need to check text generated by another model. - The user asks to "humanize", "rewrite", or "remove the AI traces". - Text is being prepared for publication (article, post, email, document). - The text contains unambiguous copy-paste chatbot markers: `:contentReference[oaicite:N]`, `?utm_source=chatgpt.com`, `grok_card://`, and similar. ## When not to use - Text that is not in English. Decline and ask for English. - Source code, configuration files, technical logs. This skill is for connected prose only. - Legal documents, statutes, contracts — there officialese is mandatory by genre. - Literary prose, poetry, literary essays — there the em-dash, the rule of three, and complex syntax may be an authorial device, not a machine tell. See `references/false-positives.md`. ## Decision tree ``` Received text ↓ Is it English? — no → decline ↓ yes Genre? — code / config → decline — contract / statute → apply only #16-21 (style/markup); do NOT touch #8 officialese — fiction / poetry → do NOT apply #13 rule of three, #16 em-dash; see false-positives.md — academic / scientific → do NOT count passive voice, hedges, logical connect...

Details

Author
khasky
Repository
khasky/awesome-agent-skills
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

humanizer-en

Use when: the user asks you to check, rewrite, humanize, or de-slop English text that shows signs of AI generation (ChatGPT, Claude, Gemini, Grok, DeepSeek, GPT-5, Qwen, Llama, any LLM). Trigger for requests like: 'humanize this', 'make it sound human / natural', 'remove the AI voice', 'this reads like a chatbot', 'AI detector for English', 'check for AI', 'de-slop', 'reduce AI-isms', remove clichés / filler / corporate jargon / emoji bullet lists 🚀 / gratuitous em-dashes / sycophantic tone / fabricated sources. Also when visible copy-paste chatbot markers are present: `:contentReference`, `?utm_source=chatgpt.com`, `oai_citation`, `grok_card://`, `vertexaisearch`, `turn0search`, `[cite_start]`, `[cite: 8]`. Do NOT use: text that is not in English, source code / scripts (even about NLP), legal documents (officialese is the genre), literary prose / poetry / résumés (there the em-dash, rhythm and compression are an authorial device).

2 Updated today
khasky
Code & Development Listed

humanizer

Remove signs of AI-generated writing from text, and write in a human voice when producing new text. Use when the user says "humanize", "make this sound human", "rewrite this so it doesn't sound like AI", "fix the AI writing", "clean up AI text", or anything similar. Also applies when editing or reviewing text to make it sound more natural and human-written. This is an always-on style skill: once activated in a conversation, apply it to everything written going forward — not just rewrites. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, filler phrases, and reflexive summary openers.

0 Updated 1 weeks ago
Hiirocchi18
AI & Automation Solid

humanize-english

Make AI-generated English text sound natural and human. Use when: writing blog posts, articles, marketing copy, any English content that must not read as AI-generated. Covers: burstiness, perplexity, banned words, sentence patterns, transitions, tone. Based on: Liang et al. (arxiv 2406.07016, 15M+ abstracts), GPTZero/Originality research. Use BEFORE publishing any AI-generated English text. Do NOT use for Russian text (use humanize-russian) or for macro-level article structure such as thesis/proof balance or a limitations block (use article-structure-review); this skill operates at the word/sentence level on English only.

138 Updated today
AnastasiyaW