<!-- source: newsletter-writer — https://raw.githubusercontent.com/mohitagw15856/pm-claude-skills/main/skills/newsletter-writer/SKILL.md -->

Newsletter Writer Skill

A newsletter is a relationship, not a broadcast. The best issues open a loop in the subject line, reward the open in the first sentence, deliver one clear idea, and make the next step obvious. This skill writes that issue — in your voice, ready to send.

Working from a brief

Given a topic, notes, or a piece to adapt, write the full issue anyway. Infer the audience and the single idea; mark invented specifics (assumed — replace). Don't hedge with "in this issue we'll explore…" — get to the value.

Required Inputs

Ask for (if not already provided):

• Topic / notes / source for the issue
• Audience and voice (or pull from a creator-brand-kit]])
• Goal / CTA (reply, click, subscribe-upgrade, share) and rough length
• Platform (Substack / beehiiv / ConvertKit / plain email) for formatting norms

Output Format

Subject lines

5 options, mixing curiosity, specificity, and benefit — each ≤ ~50 characters. Star the recommended one.

Preview text

One line (~80 chars) that complements (doesn't repeat) the subject.

The issue

• Hook — first 1–2 sentences that reward the open and set up the idea.
• Body — one core idea, in short scannable paragraphs/sub-headers, with a concrete example or story. No throat-clearing.
• The takeaway — the one thing to remember, stated plainly (a callout line works well).
• CTA — a single clear next step matching the goal.
• PS — optional, often the most-read line; use it for a secondary nudge or personal note.

Skim test

A 3-bullet "what a 5-second skimmer takes away" — if those bullets don't carry the value, restructure.

Quality Checks

• ] Subject lines are specific and varied; the preview complements, not repeats
• ] The first sentence rewards the open (no "hope you're well, in today's issue…")
• ] One core idea, skimmable, with a concrete example
• ] A single clear CTA tied to the goal
• ] Reads in the creator's voice, not generic newsletter-ese

Anti-Patterns

• A subject line that's a label ("Newsletter #42")
• Burying the value under a long personal preamble
• Three competing CTAs, or none
• A wall of text with no sub-heads or callout — unskimmable