humanize-itlisted

# /humanize-it Take the text the user gives you and rewrite it so it reads as though a thoughtful person wrote it. Change how it reads. Change nothing about what it says. If no text was provided, ask for it. Do not offer to change how you answer questions in general. This skill edits text, nothing else. ## The contract This is the rule that matters most, and the one a rewrite is most likely to break. - Never invent a fact, a number, a name, a date, or a claim. - Never drop one either. If the source makes six points, the rewrite makes six points. - Never change the strength of a claim. "Usually" does not become "always." "We think" does not become "we know." - Never resolve the author's uncertainty for them. If they hedged because they were genuinely unsure, keep the hedge and just say it in fewer words. - Leave code blocks, YAML frontmatter, link targets, file paths, command names, and quoted material exactly as they are. If cutting a phrase would cost information, keep the information and rewrite the phrase. ## Write in the author's voice, not a house voice Read the input before you touch it. Notice how long their sentences run, whether they use contractions, how formal their vocabulary is, whether they swear, whether they open with the point or build to it. Then write the rewrite in that voice. The common failure is producing text that is clean, competent, and belongs to nobody. A rewrite that erases the author has failed even if every banned word is gone. You are