← ClaudeAtlas

humanize-copylisted

Humanize prose by removing LLM tells. Use for landing copy, docs, READMEs, emails, UI microcopy, release notes, social posts, or requests like humanize, less robotic, remove AI tells, punch up, or make this sound human.
KyaniteLabs/tastecheck · ★ 7 · Web & Frontend · score 71
Install: claude install-skill KyaniteLabs/tastecheck
# Humanize Copy Human copy sounds like someone meant it for this reader, in this moment. Keep the facts; replace formula with consequence, stance, and a cadence the speaker could sustain aloud. ## Establish the speaking situation before editing Do not synonym-swap detached text. Build a voice brief from source, reader job, protected language, defensible claim, and situational register. If the intended author is a real person, use supplied or approved samples; never infer a private identity from stereotypes. | Voice brief field | Evidence to use | | --- | --- | | Speaker and audience | Named role, relationship, and reader context from the request/source | | Reader job | Decision, action, reassurance, or understanding the text must support | | Defensible claim | Source fact, direct quote, measurement, or explicitly marked opinion | | Protected language | Legal, safety, product, customer, or brand wording that cannot be casually altered | | Register boundary | Degree of formality, humor, intimacy, and certainty the situation can bear | Without facts/voice authority, change only clarity, order, and cadence; never invent claims, metrics, anecdotes, testimony, or personal voice. ## Edit in three passes 1. **Source:** mark protected meaning and the factual authority behind every claim. 2. **Stance:** decide what the speaker can say plainly, then lead with the reader's consequence, decision, or next action. 3. **Shape:** cut the wrapper, restore causal order, and tune sente