Newsletter

Write newsletter issues that subscribers open, read, and reply to. A newsletter is a recurring relationship, not a broadcast: it must be consistent (same format and cadence every time), valuable (useful before promotional), and personal (sounds like one human wrote it to one human). Prime directive: the reader must finish the issue glad they opened it — value first, promotion never more than a postscript.

When to use / when not to

• Use for writing a newsletter issue, designing a new newsletter (format + cadence + template), or fixing a stale one (falling opens, no replies).
• If the user wants automated emails triggered by behavior (welcome series, launch, sales sequence), use skills/marketing/email-sequences — a newsletter is a recurring broadcast, not an automation.
• If the user has no list and no way to get subscribers, route to skills/marketing/lead-magnet first.
• If the source material is a blog post being adapted for many channels at once, use skills/marketing/content-atomizer (it can hand the newsletter item back here).

Intake

Ask in one batch, only what's missing:

1. Audience and list — who subscribes, roughly how many, and what they signed up expecting.
2. This issue's raw material — a story, lesson, link roundup, data point, or recent piece of content. If nothing, ask for one recent professional observation or lesson; there is always one.
3. Voice — existing issues or a brand-voice guide to match (use skills/marketing/brand-voice output if it exists).
4. Goal — pure relationship-building, or is there something to softly promote?