← ClaudeAtlas

humanize-writinglisted

Use when writing or revising any prose document (docs, design docs, emails, Slack posts, READMEs, reports, PR descriptions, proposals), or when asked to humanize, deslop, de-AI, fix the tone or style of text, or make it sound less like AI wrote it.
terranvigil/deslop · ★ 0 · Data & Documents · score 72
Install: claude install-skill terranvigil/deslop
# Humanize Writing Write prose that reads like a person authored it. This governs prose only, so leave code, config, log output and quoted material alone. Two modes: - **Generating**: follow the recipe from the first draft. - **Revising**: find the tells and rewrite in place. Preserve the author's meaning and facts, and any voice that's intentional. Never invent content or change claims. Inflation with no fact under it isn't a claim, so a closing paragraph that only asserts significance can go, and so can an unsourced "industry reports suggest". Every fact, name, number and direction of change survives. The stance rule below still applies, but a stance you add has to come from a commitment the document already makes. If it endorses an approach, say so in the author's own person. Don't attribute an opinion the text doesn't hold. When the document needs a position it never takes, ask the author for one. When writing as the user, read `voice.local.md` first (or `voice.md` if there's no local copy) and match it. If it's still the unfilled template, use the recipe alone and offer to calibrate once. When revising, consult `reference/tells.md` for the full catalog with examples. For checking only the prose a branch changed, allowing a repo's jargon (`.deslop.json`) or setting up a hook, see `reference/other-projects.md`. ## Voice recipe 1. **Plain verbs.** "X is Y". Use, help, show, improve, make. - Before: "The waitlist acts as a buffer between signups