Humanize — скилл

---
name: humanize
description: >
  Use whenever the user asks to "humanize", "make this sound more human", "rewrite to
  avoid AI detection", "make this less AI-sounding", "add a human voice", or "write like
  a person". Also use when the user pastes text and asks why it reads as robotic, generic,
  flat, or AI-like, or when generating new text in a register where AI tells (em dashes,
  semicolons, hedges, banned vocabulary like "delve", "leverage", "robust") would damage
  credibility.
---

# Humanize Text Skill

Transforms AI-generated or flat text into output that mirrors the statistical and stylistic
fingerprint of human writing. Grounded in the published detection literature; sources live in
`references/research.md` (background only, not needed during a rewrite).

---

## Hard rules (read first, enforce last)

These seven fail more often than everything else combined, because the model that wrote the
draft is the model checking it. You systematically overproduce these patterns; your draft
contains em dashes even when you don't remember writing them. Treat "my draft is probably
clean" as false by default.

1. **Em dashes:** at most one per 300 words of output. Under 300 words, zero.
2. **Semicolons:** none, unless a list item itself contains commas or the register is
   explicitly formal/academic (Lever 8).
3. **Straight quotes and apostrophes only.** Never curly. Sole exception: publishing
   contexts where typographic quotes are house style (Lever 8).
4. **Banned vocabulary** (full list at end of this skill). Highest-frequency offenders:
   delve, leverage, utilize, robust, comprehensive, streamline, furthermore, moreover,
   "it is important to note".
5. **No negation framing:** "not just X", "not X, it's Y", "it's not about X, it's about Y",
   "more X than Y". Say what the thing IS. Poetic forms count: "isn't proof you failed,
   it's proof you showed up" is the same banned pivot wearing a nicer coat. (False binaries
   like "either X or Y" are handled by the Signal I checklist's either/or item.)
6. **Output shape:** the rewritten text only. No preamble ("Here's the humanized version:"),
   no trailing changelog ("Main moves:", "What I changed:"). The ONLY permitted additions
   are the two meta-notes mandated by protocol steps 2 and 5.6, appended after the rewrite.
   If the user wants the diff explained, they'll ask.
7. **Sentence-length spread:** in any output over ~80 words, the longest sentence must beat
   the shortest by 20+ words, and fewer than half the sentences may sit in the 10-to-20-word
   band. Your uncorrected rhythm clusters at 10-20 words with ~6 words of deviation; that