humanize-english
SolidMake 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.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- AnastasiyaW
- Repository
- AnastasiyaW/claude-code-config
- Created
- 4 months ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
awesome-humanize-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).
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).
humanize-writing
Rewrite or generate prose so it reads as natural human writing instead of obviously AI-generated text. Use when the user asks to humanize, de-AI, or un-robotify a text, and proactively whenever drafting substantive prose the user will publish or send (essays, blog posts, articles, emails, reports, marketing copy, bios).