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
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
Example Trigger Phrases
- "Write a newsletter."
- "Write this week's Substack issue."
- "Turn these notes into a sendable newsletter."
- "Write a subject line and hook for my email issue."
1---2name: newsletter-writer3description: "Write a full creator newsletter issue — subject line, preview text, hook, body with a clear takeaway, and a CTA — in the writer's voice, for Substack, beehiiv, ConvertKit, or email. Use when asked to write a newsletter, an email issue, a Substack post, or to turn notes/a topic into a sendable newsletter. Produces a ready-to-send issue with subject-line options and a skimmable structure. Distinct from B2B drip/nurture sequences."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/newsletter-writer7---89# Newsletter Writer Skill1011A 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.1213## Working from a brief1415Given 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.1617## Required Inputs1819Ask for (if not already provided):20- **Topic / notes / source** for the issue21- **Audience** and **voice** (or pull from a [[creator-brand-kit]])22- **Goal / CTA** (reply, click, subscribe-upgrade, share) and rough **length**23- **Platform** (Substack / beehiiv / ConvertKit / plain email) for formatting norms2425## Output Format2627### Subject lines28**5 options**, mixing curiosity, specificity, and benefit — each ≤ ~50 characters. Star the recommended one.2930### Preview text31One line (~80 chars) that complements (doesn't repeat) the subject.3233### The issue34- **Hook** — first 1–2 sentences that reward the open and set up the idea.35- **Body** — one core idea, in short scannable paragraphs/sub-headers, with a concrete example or story. No throat-clearing.36- **The takeaway** — the one thing to remember, stated plainly (a callout line works well).37- **CTA** — a single clear next step matching the goal.38- **PS** — optional, often the most-read line; use it for a secondary nudge or personal note.3940### Skim test41A 3-bullet "what a 5-second skimmer takes away" — if those bullets don't carry the value, restructure.4243## Quality Checks4445- [ ] Subject lines are specific and varied; the preview complements, not repeats46- [ ] The first sentence rewards the open (no "hope you're well, in today's issue…")47- [ ] One core idea, skimmable, with a concrete example48- [ ] A single clear CTA tied to the goal49- [ ] Reads in the creator's voice, not generic newsletter-ese5051## Anti-Patterns5253- A subject line that's a label ("Newsletter #42")54- Burying the value under a long personal preamble55- Three competing CTAs, or none56- A wall of text with no sub-heads or callout — unskimmable5758## Example Trigger Phrases5960- "Write a newsletter."61- "Write this week's Substack issue."62- "Turn these notes into a sendable newsletter."63- "Write a subject line and hook for my email issue."