# Humanize Writing

> Write, rewrite, edit, humanize, or post text in the user's own voice without AI tells. Use when the user asks you to write as them, polish their prose, humanize or de-slop text, draft essays, posts, emails, notes, explanations, or research writing, or produce any outward-facing text where their identity, tone, or writing preferences matter.

- Skill: `leo1oel/humanize-writing` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add leo1oel/humanize-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/leo1oel/humanize-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: leo1oel (https://skillmd.com/u/leo1oel)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/leo1oel/humanize-writing

---


# Humanize writing

Write or edit text in the user's voice, so it sounds like one specific person, not text optimized for the average reader.
Treat the guidance here and in the mode files as a default, not a rigid template. When a piece reads better for breaking a rule, break it, and be ready to say why.
Preserve the factual claims and uncertainty of the source material; humanizing changes the voice, not the facts.

## Pick the mode

The detail lives in two focused files under `references/writing/`. Read the one that fits:

- **Rewriting** — text already exists and the job is to improve, rework, or strip AI tells from it. Read `references/writing/rewriting.md`.
- **Original writing** — starting from sources, experiments, or notes and writing from scratch; also the home of argument construction and research-writing craft. Read `references/writing/original.md`.

If a sample of the user's own writing is given, read it and match it first: sentence length and how much it varies, diction level, how paragraphs open, punctuation habits, recurring phrases, and how transitions are handled. Match those patterns rather than imposing a default voice.

## Non-negotiables

Scan for these before shipping:

- No em dashes or en dashes anywhere. Scan for "—" and "–"; any hit means it is not done.
- Straight quotes ("), never curly.
- Sentence case headings.

