anti-ai-detection-writing-skill
Anti-AI Detection Writing Skill
Make AI-written prose easier and more natural to read while preserving its meaning. For a high-stakes formal letter, the top-level recommendation is that a human chooses the words of the whole document and that AI is used only for fact checks and small fixes. Improve flow, specificity, and tone for the intended audience. For a short private retailer or customer-service email, answer the latest question first, preserve every supplied fact and qualification, make one clear ask, and use ordinary words. When the user explicitly requests detector testing, work toward lower scores through useful edits and measure the outcome, except for a high-stakes formal letter, where a flagged chunk goes back to a human and AI stays limited to fact checks and small fixes. Never trade accuracy or readability for a score. When they conflict, report both and keep natural, fact-complete English. A fluency polish of a scored draft is a new text, and a paragraph score is not the assembled document's score: rescan the exact final bytes. Detector results do not establish human authorship, inbox delivery, or permission to publish. A lower score is a comparison between comparable scans, not a property of one result or of an unmeasured edit.
High-stakes formal writing
Use this section for a recommendation letter or another high-stakes formal letter to an expert reader. It is the top-level recommendation for that writing. A human chooses the words of the whole document. Use AI only to check facts and to make small fixes. A short private retailer or customer-service email stays in its own section. Other prose stays in Write and review. The surface-stat limits in this section also apply there.
[our scans; n=1] On 17 November 2026, free-plan GPTZero 5.0b, one scan per text, read in the Basic view: one human-written recommendation letter of 365 words scored 1% AI / 99% mixed and was labelled "AI Polished". An AI baseline of 428 words and 9 whole-letter rewrites all scored 100% AI. The writer's raw edit shared about 4% of its 4-grams with the AI draft. The adopted text kept a character similarity of 0.90 to that raw edit. The human letter does not say the same things as the AI drafts: the comparison's writer cut some facts, and this skill does not copy that cut. This is one human letter. It is not a way to pass GPTZero. The public record is the 17 November 2026 letter comparison.
Keep every fact, uncertainty, and qualification. Never invent a fact, an error, or a typo. Do not copy outside text word for word as a technique.
[newer evidence for this letter; older email evidence kept] Stages 28–31 (16–17 November 2026) are the older short-email record. They say to polish a human draft lightly and keep similarity at roughly 0.75 or higher. That 0.75 is 1 − Levenshtein/max_len on public Enron emails, and it was not tested on long documents. It is not this letter's 0.90 character similarity. Both figures stay. For a high-stakes formal letter, this 17 November letter is the newer evidence: a human chooses the words, and AI stays on fact checks and small fixes. Do not read the email light-polish note as permission to polish this kind of letter. Stages 32–34, whose calendar date was not in the supplied record, say to edit the writer's own draft lightly and keep phrasing and structure that already works. They also say that keeping one human sentence word for word is not a technique. Stage 41, noted with those stages on 17 November 2026, added two of the recommender's own public posts verbatim to an AI-drafted recommendation letter and left it at 100% AI. That agrees with the ban on copying outside text. Those email rows stay. None of this lowers the score of a document that starts AI-written. No letter text is recorded.