What problem does it solve? Drafts of docs, site copy, and chat replies often read as machine-generated: long sentences, em-dash sprinkling, hype adjectives, and negation-contrast phrasing. This Skill provides a standing style guide that rewrites such text into plain, human prose and keeps supporting evidence out of reader-facing pages. ## Core Features & Use Cases - Plain English base rules: Enforces short sentences (15-20 words), active voice, everyday words, and a substitution table for jargon (e.g. "utilise" to "use"). - LLM-voice tell removal: Cuts em-dash stacking, "not X, it's Y" constructions, announced-honesty preambles, colon reveals, anthropomorphized tools, and hype words like "seamless" or "robust". - Reader-facing surface structure: Leads README and site pages with the benefit and headline fact, then links out to REPORT_.md, RUNBOOK_.md, and PLAN_*.md files for the proof. - Use Case: Before publishing a new README section or runbook, run the five-step edit workflow to split long sentences, remove machine-voice tells, and check that methodology does not appear before the benefit. ## Quick Start Review this draft paragraph using the plain-prose rules and rewrite it in plain, human prose.
