← ClaudeAtlas

writing-english-proselisted

Remove AI writing patterns from English prose, or flag them without rewriting. Use when drafting, editing, reviewing, or proofreading US-English text (essays, posts, docs, emails, UI strings, locale files), and when asked whether a text sounds AI-written. Fluent, natural American English.
qiaeru/skill-english-prose · ★ 1 · Data & Documents · score 69
Install: claude install-skill qiaeru/skill-english-prose
# Writing English Prose Write English that reads like a good human writer, not like a model. Two failure modes count as slop. The first is the familiar AI gloss: filler phrases, formulaic contrasts, empty intensifiers, signature vocabulary, pull-quote bait. The second is overcorrection: prose compressed into six-word slogans until it reads like a LinkedIn post. The target sits between them: fluent, natural US English, with concrete subjects, real verbs, and rhythm that varies because the ideas demand it. ## When to apply Apply to essays, blog posts, documentation, READMEs, emails, announcements, and any professional prose in US English. Skip fiction, poetry, lyrics, legal text, and direct quotes, where these rules would flatten a deliberate voice. Register target: plain American magazine prose (a good engineering blog, The Atlantic, a Paul Graham essay), conversational but precise. Contractions are normal written English; use them. That register is the default for a text that chooses none; when the source holds its own (a casual post, an internal note, an email between colleagues, a technical manual), keep it and fix the tells inside it, without pulling the text up toward the default. Informality already in the source is voice; informality added by the correction is the over-corrected register described in [references/structures.md](references/structures.md). An interface file (application labels, locale files) mixes fragments (buttons, field labels) with full sentences, w