Humanize Text

Humanize-text

Make the text fit its reader, purpose, and speaker. Remove mechanical habits where they get in the way; do not manufacture a statistical fingerprint of a human.

For an ordinary rewrite, use information-editing as the primary operation. For new prose, retain information-writing; a technical document, status report, or presentation keeps its artifact-specific owner. This skill supplies the voice and surface-style pass, not a new research, evidence, or document workflow. Load only the relevant owner, not the whole writing family.

Explicit instructions, source fidelity, required format, accessibility, and house style take precedence over these defaults. A request for light editing does not authorize a structural rewrite. Preserve the language and useful personality of the input; natural writing need not be casual, terse, or emotionally neutral.

Read the whole text before changing it. Identify its intended reader and register from the supplied context. If writing samples are provided, observe their diction, rhythm, and degree of formality as provisional style cues; do not import their events or claims into the new text.

Locate the passages that sound mechanical and repair those passages. Keep good sentences. For a new draft, apply the same choices while writing:

• Start with useful content. Remove empty acknowledgments, announcements of what the answer will do, generic praise, and ceremonial conclusions. Keep an introduction or recap when it helps a reader enter or navigate a long document.
• Let the content choose the shape. Use prose for connected reasoning. Keep bullets for genuinely separable items, ordered steps for procedures, and tables for comparisons. Do not convert everything into lists or flatten a useful checklist into a paragraph. Use headings and bold only where they aid reading.
• Do not force groups of three. Choose examples and arguments for what each adds. Remove a redundant third example; retain three when all three matter. Never invent another item merely to make a list look less symmetrical.
• Vary rhythm where it helps meaning. Split an overloaded sentence; join repetitive fragments when their relationship becomes clearer. Do not count sentence lengths, insert obligatory fragments, or stretch sentences to meet a variance target. Coherence is worth keeping.
• Use the words the subject needs. Prefer a precise verb to inflated phrasing. Keep necessary technical terms and stable names for the same thing. Do not cycle synonyms for variety or ban ordinary words because they appear in AI output.
• Cut rhetorical machinery when it adds no information. Watch repeated "not X but Y" pivots, matched openings, grand claims, and punchline endings. Keep a real contrast, parallel construction, or memorable line that serves the argument. Do not introduce false asymmetry into a balanced comparison.
• Keep useful connections. Remove stock transitions when the relationship is already clear. Retain causal links, conditions, and reminders the reader needs. Do not deliberately add a digression, unresolved thought, or awkward connection.

Prefer a period, comma, or a shorter construction to repeated long em dashes (—). When a dash is useful in ordinary chat or informal copy, default to a plain spaced dash (-); use the required typography in edited or publication-ready prose. Do not globally replace punctuation in quotations, code, identifiers, URLs, mathematical notation, negative numbers, or ranges. Preserve grammatical hyphens.

Semicolons, colons, and typographic quotation marks are not evidence of machine authorship. Use them when they serve the sentence and language conventions; preserve Russian «кавычки» and specified house style. Avoid decorative punctuation without imposing quotas or an English-only typography rule.

Match conversational features to the actual speaker and channel. Contractions or direct address may fit an informal message; forced slang, all-lowercase text, staged self-corrections, and deliberate errors usually do not. Do not insert "in my experience" or a personal anecdote without a supplied factual basis.

Keep facts, attribution, quantities, time frames, scope, commitments, and material limitations unchanged. Remove an empty hedge, but keep uncertainty supported by the evidence. "May reduce failures" must not become "prevents failures" for a more confident voice. Preserve caveats and opposing evidence that affect a decision.

Use specifics only when the input or authorized sources support them. Do not invent metrics, named customers, quotes, dates, or lived experience to make prose feel authentic. If a missing detail blocks the requested result, ask for it or mark a placeholder when appropriate. A clearly labeled hypothetical example must remain hypothetical. Do not add new research merely for this style pass.

Judge the result by readability and fidelity, not a detector score. Do not run detectors, add watermark or character tricks, tune decoding parameters, or create a multi-model pipeline as part of this skill. Do not promise undetectability, claim human authorship, or remove required AI-use disclosures or source credit.

• Empty framing: "Важно отметить, что отправить заявку можно до пятницы." → "Заявку можно отправить до пятницы." The deadline and modality stay intact.
• Decorative dash: "Заявка принята — ответ придёт завтра." → "Заявка принята. Ответ придёт завтра." Do not weaken or strengthen the promise.
• Useful short list: "Bring your passport, ticket, and insurance policy." Keep all three requirements; the number three is not itself a defect.
• Missing evidence: "The new cache may improve latency." Do not rewrite it as "We cut latency by 40%." Ask for measured results only if the task needs them; otherwise preserve the qualified claim.

Read the revised text once against the original: did any condition, useful detail, logical connection, or distinctive voice disappear? Did removing a template introduce another one? Correct material drift, then stop. No scorecard, word-count gate, or repeated audit loop is required.

For a rewrite, return the revised text by default. Explain choices when asked, and briefly flag a material unresolved ambiguity when needed. A short diagnostic request needs a diagnosis, not an unsolicited full rewrite.