Edit text for plain, direct language: cut hedging words ("perhaps", "in order to", "it should be noted that"), shorten sentences, prefer active voice and concrete nouns over abstractions. Use when the user asks to "tighten this up", "make this clearer", "cut the fluff", or pastes a draft blog post, email, or announcement for a plain-language pass. Do NOT use for legal, medical, or technical reference text where precise qualifying language is load-bearing — cutting a hedge there can change the meaning, not just the style.

# Clear writing Edit prose for plain, direct language without changing its meaning. ## When to use - The user asks to "tighten this up", "make this clearer", "cut the fluff", or "make it punchier". - A draft blog post, changelog entry, announcement, or email reads stiff, hedgy, or padded with filler. ## Do NOT use for - Legal, medical, compliance, or technical reference text where a qualifying word ("may", "should", "under certain conditions") carries real meaning. Cutting a hedge there changes what the text asserts, not just its style. - Code, config, or data — this skill edits prose only. ## How to edit 1. **Cut hedging and filler.** Remove "in order to" -> "to", "it should be noted that" -> delete, "perhaps" / "sort of" / "basically" -> delete unless genuinely uncertain, "at this point in time" -> "now". 2. **Shorten sentences.** One idea per sentence. Split any sentence with more than one comma-joined independent clause. 3. **Prefer active voice.** "The report was written by the team" -> "The team wrote the report." Passive voice is fine when the actor is genuinely unknown or unimportant — don't force it everywhere. 4. **Use concrete nouns.** "Leverage synergies to drive engagement" -> name the actual thing that happened. 5. **Cut redundant qualifiers.** "very unique", "completely finished", "totally clear" — the qualifier adds nothing. 6. **Read it aloud.** If a sentence is hard to say in one breath, split it. ## What NOT to cut - Specific numbers, names, dates, and caveats that change what's true. - Voice and personality — clear does not mean flat. Keep the author's actual point of view; cut what's in the way of it. ## Examples **Before:** "It should be noted that, in order to improve the overall user experience, we have made the decision to leverage a more streamlined onboarding flow going forward." **After:** "We shortened onboarding to improve the experience." **Before:** "There are a number of different ways that this particular feature could potentially be utilized by users in various scenarios." **After:** "Users can use this feature several ways."