genstarters
Task New #newsletter#writing#editing

Newsletter Editor

Edits a rough newsletter draft into something people will actually read to the bottom. Cuts filler, sharpens claims, respects the writer's voice.

The prompt

I'll paste a newsletter draft. Edit it. Return the edited version + a diff summary.

Editing rules:

1. **Subject line** — if I have one, sharpen it (under 60 chars, front-load the value, no clickbait). If I don't, propose 3 options.
2. **Opening** — cut any "hey folks, hope you had a great week" preamble. Start with the substance.
3. **Body** — for each paragraph:
   - Kill filler words: "just," "really," "very," "actually," "basically," "in order to," "at the end of the day."
   - Cut sentences that could be deleted without losing meaning.
   - Break up 4+ sentence paragraphs.
   - Preserve specific claims, numbers, names, and voice.
4. **Structure** — if it wanders, suggest one restructure. Don't do a heavy rewrite unless I ask.
5. **CTA** — if the newsletter has an ask (reply, click, subscribe), make sure it's clear and lands at the end.

Output:

**Edited version** — the whole thing, ready to send.

**Diff summary** — 5 lines max: what you cut, what you sharpened, what structural change (if any) you'd suggest.

**Cuttable if too long** — mark 2-3 paragraphs that could be cut if I want it shorter, and why.

Rules:
- Don't rewrite my voice. If I'm casual, stay casual. If I'm sharp, stay sharp.
- Never invent claims or numbers.
- If a sentence doesn't work but I clearly meant something specific, ask what I meant rather than guess.

## How to use it

Paste this prompt, then paste your draft. Read the diff summary before accepting; that's where you'll spot anything you actually want to keep.

## Why it works

Most newsletter drafts are 20-30% too long. A structural edit that preserves voice and tightens sentences typically doubles the read-to-end rate without changing what you're saying.

How to use it

I’ll paste a newsletter draft. Edit it. Return the edited version + a diff summary.

Editing rules:

  1. Subject line — if I have one, sharpen it (under 60 chars, front-load the value, no clickbait). If I don’t, propose 3 options.
  2. Opening — cut any “hey folks, hope you had a great week” preamble. Start with the substance.
  3. Body — for each paragraph:
    • Kill filler words: “just,” “really,” “very,” “actually,” “basically,” “in order to,” “at the end of the day.”
    • Cut sentences that could be deleted without losing meaning.
    • Break up 4+ sentence paragraphs.
    • Preserve specific claims, numbers, names, and voice.
  4. Structure — if it wanders, suggest one restructure. Don’t do a heavy rewrite unless I ask.
  5. CTA — if the newsletter has an ask (reply, click, subscribe), make sure it’s clear and lands at the end.

Output:

Edited version — the whole thing, ready to send.

Diff summary — 5 lines max: what you cut, what you sharpened, what structural change (if any) you’d suggest.

Cuttable if too long — mark 2-3 paragraphs that could be cut if I want it shorter, and why.

Rules:

  • Don’t rewrite my voice. If I’m casual, stay casual. If I’m sharp, stay sharp.
  • Never invent claims or numbers.
  • If a sentence doesn’t work but I clearly meant something specific, ask what I meant rather than guess.

How to use it

Paste this prompt, then paste your draft. Read the diff summary before accepting; that’s where you’ll spot anything you actually want to keep.

Why it works

Most newsletter drafts are 20-30% too long. A structural edit that preserves voice and tightens sentences typically doubles the read-to-end rate without changing what you’re saying.

✦ More like this

Related prompts