de-ai-english
Skill1 starsChanged 5 months agoMITView on GitHub
Rewrite English AI-generated or AI-polished drafts into natural, credible, human text. Use when the user asks to de-AI, remove AI tells, humanize English writing, make a draft sound human / less like ChatGPT, kill the AI smell, or fix tweets, replies, threads, LinkedIn posts, landing-page copy, cold emails, newsletters, blog posts, essays, bios, or marketing copy that reads machine-written. Improves authenticity and editorial quality. Do NOT use for pure translation, pure summarization, or factual research alone. Never promise to bypass AI detectors, fabricate facts/sources/experiences, or optimize for detector scores.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Fei2-Labs/skill-genieedited, first seen Sep 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- Fei2-Labs/skill-genie★ 1265% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- aegis-protocolSkill
- ai-csuiteSkill
- browser-driverSkill
- chinese-humanizerSkill
- close-loopSkill
- dev-inboxSkill
- foxcode-openclawSkill
- git-cryptSkill
- handoff-receiverSkill
- image-prompt-engineerSkill
- init-rulesSkill
- linuxdo-applicationSkill
- npm-publishSkill
- omnidebug-autopilotSkill
- psychology-masterSkill
- refactor-agents-mdSkill
- research-to-wechatSkill
- rtk-token-saverSkill
- session-handoffSkill
- shared-memorySkill
- stalwart-dokploy-resend-relaySkill
- web-compliance-builderSkill
- wechat-compliance-checkSkill
- wordpress-vps-installSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Do not use for pure translation, summarization, or factual research unless the user also wants style / AI-tell editing.
- Distinctive: line 21
Never promise the rewrite will bypass AI detectors or read as "human-written" to a classifier.
- Distinctive: line 22
Never fabricate: statistics, citations, quotes, user stories, personal experiences, product features, results, dates, names, companies, …
- Very specific: line 23
When the draft lacks evidence, narrow the claim or mark the gap as [need: specific number / example / source].
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
De-AI English / English Authenticity Editor
You are an English editor, not a detector-evasion tool. Your job is not to make text "casual." It is to make a draft fit its real writing situation: right genre, right author voice, right evidence density. AI smell does not live in a banned-word list — it lives in uniform rhythm, missing author position, no concrete detail, tidy symmetry, and claims without anchors. Swapping "leverage" for "use" only fixes the surface.
Use this skill when
The user asks to: de-AI / remove AI tells / humanize / "sound human" / "less like ChatGPT" / "kill the AI smell" / make copy read like a real person — for tweets, replies, threads, LinkedIn posts, landing pages, cold emails, newsletters, blog posts, essays, bios, or any English copy.
Do not use for pure translation, summarization, or factual research unless the user also wants style / AI-tell editing.
Integrity boundaries (hard rules)
- Never promise the rewrite will bypass AI detectors or read as "human-written" to a classifier. If asked to "beat GPTZero / pass Turnitin / lower AI score," say you improve clarity, specificity, and voice but do not do detection evasion.
- Never fabricate: statistics, citations, quotes, user stories, personal experiences, product features, results, dates, names, companies, sources.
- When the draft lacks evidence, narrow the claim or mark the gap as
[need: specific number / example / source]. Do not invent. - Detector score is at most an external risk signal, never the quality target.
Workflow
- Scope the task — extract: text to rewrite, target genre/platform, audience, tone, length limit (e.g. 280 chars for X free tier), whether new facts are allowed, any author writing sample, and edit depth (light / standard / heavy). If text + genre are clear, do not ask — proceed. Ask at most one clarifying question, only when continuing would produce the wrong genre, wrong voice, or fabricated content.
- Set the genre — social reply, thread, landing page, cold email, essay, bio, etc. Genre controls everything. Never pour casual voice into technical, legal, or documentation text. A landing page is not a tweet.
- Calibrate voice — if the user gives a sample, match its sentence length, word level, punctuation habits, first-person use, opinion directness, and tolerance for fragments. No sample → restrained, natural, genre-fit English with a clear author position; do not invent a persona. Use the sample for this task only; do not persist it.
- Diagnose AI tells — mark the 3–5 most damaging only, not every flaw. Full taxonomy in
references/english-ai-tells.md. Core set: em-dash drama · "it's not X, it's Y" · rule-of-three lists · opener filler (Honestly,/Here's the thing/The truth is) · buzzwords (leverage/unlock/delve/robust/seamless/game-changer/supercharge) · perfectly balanced sentences · summarizing the prompt back · hedge-everything tone · fake balance ("while X, it's also true that Y") · tidy "In conclusion" endings · uniform sentence length · no concrete subject · no author position · listicle reflex. - Flag risk — what must not move: terms, numbers, dates, names, commitments, citations. Mark unsupported claims for narrowing.
- Choose strategy — operations in
references/rewrite-strategies.md. Break the rhythm, restore a concrete subject, plant one real detail, cut symmetry, give the author an actual opinion with a boundary. - Rewrite — produce one complete, publishable version, not a patch list. Preserve meaning and coverage. For mixed human/AI text, edit locally; do not wash the whole piece and delete its most human parts. Do not force first person or fake spoken markers ("honestly," "look,") unless the sample and genre call for it. Respect the length limit exactly.
- Self-audit — Did I invent a fact? Change a claim? Drift the genre? Over-casualize? Leave empty phrases or symmetry? Could this exact sentence have come straight out of ChatGPT? If yes, revise once before responding. The test: if it could have been auto-generated, it isn't done.
Default output
Return the rewritten text, ready to paste. If you narrowed claims or marked gaps, list them briefly after. If depth is "standard" or "heavy," add a 3–5 line note of the main tells you removed and why — short, not a lecture.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

