Skip to content This library is free, offered as dana. If it helps your work, donate here →
penguin tree ai
← back to libraryDonate here

This is one of 3,622 free prompts in the penguin tree ai library. Sign up once and the whole library opens, with new prompts by email.

open the library →

Newsletter subject line generator

Generates 50 newsletter subject lines across 8 open-rate-driven strategies, each paired with matching preview text and labeled by psychological trigger and length, then ranks the top 8 for A/B testing. Use when writing…

download .md

Purpose

Generate a large, strategically varied set of newsletter subject lines — written in a tight journalistic voice and calibrated for the inbox — each paired with preview text and labeled by trigger and length, so editors always have strong, testable options instead of settling on the first line that comes to mind.

When to Use

Invoke this skill when the user asks to:

  • Write subject lines for a specific newsletter issue
  • Improve or lift a newsletter's open rate
  • Build a batch of subject lines to A/B test
  • Rework a flat or underperforming subject line
  • Generate subject line + preview text pairs for an email send
  • Find a curiosity-driven angle for a story-heavy issue

Inputs Required

Before starting, collect:

  • Newsletter topic/niche: What the publication covers
  • This issue's lead story: The single most important item in the send
  • Secondary items: 2–4 other stories or sections in this issue
  • Audience: Who subscribes and why they open
  • Voice: House tone — dry/witty, urgent/newsy, warm/personal, analytical
  • Sender recognition: Is the "from" name a known brand or a personal byline?
  • Any subject line rules: Word limits, banned phrases, emoji policy

If voice is missing, default to a tight journalistic tone. If preview text length isn't specified, target 35–90 characters.

Instructions

Generate 50 Subject Lines Across 8 Strategies

For each subject line, include:

  • The subject line (written for this specific issue — never a template with brackets)
  • Preview text: The complementary line that shows after the subject in the inbox — it should extend, not repeat, the subject
  • Trigger: The psychological driver being activated
  • Length: Character count (aim for 30–50 characters for mobile; flag anything over 60)

Keep everything short and punchy. Front-load the strongest word. Cut filler ("the," "a," "how to") whenever it doesn't earn its place.

Strategy 1 — Curiosity Gap (8 lines) Open a loop tied to the lead story that the reader can only close by opening.

  • Triggers: curiosity, intrigue, incompleteness
  • The gap must feel resolvable and specific to this issue — not vague clickbait
  • Format options: "What nobody told you about [subject]" / "The [subject] problem nobody's fixing" / "[Surprising fact]. Here's why."

Strategy 2 — News Hook / Newsy Lead (8 lines) Treat the subject like a headline on the most timely item. Direct, present-tense, active verbs.

  • Triggers: relevance, timeliness, authority
  • Lead with the strongest noun or verb; write like a wire-service headline
  • Format options: "[Subject] just [changed/broke/shifted]" / "Inside [event/development]" / "[Number] takeaways from [event]"

Strategy 3 — Number / List (7 lines) Promise a concrete, scannable payoff using a specific figure from the issue.

  • Triggers: specificity, curiosity, low-effort promise
  • Odd and specific numbers outperform round ones
  • Format options: "[N] things you missed this week" / "The [N] charts that explain [topic]" / "[N] reasons [claim]"

Strategy 4 — Direct Benefit (6 lines) State plainly what the reader gets by opening. No cleverness — pure clarity.

  • Triggers: desire, clarity, utility
  • Best for loyal audiences who open on substance, not intrigue
  • Format options: "Your [timeframe] guide to [topic]" / "Everything on [event], in one place" / "[Outcome] without [obstacle]"

Strategy 5 — Question (6 lines) Provoke self-identification or a mental answer the reader wants confirmed.

  • Triggers: curiosity, self-identification, doubt
  • No obvious yes/no answers; the question must implicate the reader
  • Format options: "Are you [common belief]?" / "Why is [phenomenon] happening?" / "What if [premise] is wrong?"

Strategy 6 — Contrarian / Tension (6 lines) Challenge a consensus view or set up a surprising conflict from the issue.

  • Triggers: surprise, contrast, challenge
  • Must be defensible by the content inside — no bait the story can't pay off
  • Format options: "Everyone's wrong about [subject]" / "[Popular thing] isn't working" / "Stop [common behavior]"

Strategy 7 — Personal / Insider Voice (5 lines) Written in a first-person byline tone, as if the editor is emailing a friend.

  • Triggers: intimacy, trust, exclusivity
  • Best when the "from" name is a person, not a brand
  • Format options: "A thing I've been thinking about" / "I was wrong about [subject]" / "Between us: [subject]"

Strategy 8 — Urgency / Time-Sensitive (4 lines) Signal that opening now matters — only when the issue genuinely warrants it.

  • Triggers: FOMO, timeliness, loss aversion
  • Never manufacture urgency; use only for time-boxed items in this issue
  • Format options: "Before [deadline]: [subject]" / "This changes [when]" / "Last look at [subject]"

Rank the Top 8 for Testing

After generating all 50, select the 8 strongest and present them as an A/B test slate:

  1. Why it works: One sentence tying the line to this issue's content and audience
  2. Strategy pairing: Note which two lines to test against each other and what variable that isolates (curiosity vs. clarity, question vs. statement, etc.)
  3. Predicted performer: Name one line as the likely winner and say why. Be opinionated.

Output Format

  • Structure: 8 labeled strategy sections with numbered subject lines; top-8 test slate as a ranked list with rationale
  • Length: 900–1,300 words
  • Format: Swipe-file style — scannable, each line tagged with preview text, trigger, and character count; not prose-heavy
  • Sections: 8 strategy lists → Top 8 test slate → Predicted performer
  • Tone: Tight journalistic voice — punchy, active, no filler; the lines themselves read like headlines

Quality Checklist

Before delivering output, verify:

  • [ ] All 50 subject lines are present (count them across strategies)
  • [ ] Strategy counts match exactly (8, 8, 7, 6, 6, 6, 5, 4)
  • [ ] Every line has preview text that extends rather than repeats the subject
  • [ ] Every line has a trigger label and a character count
  • [ ] Lines are written for this specific issue — no bracket placeholders or generic templates
  • [ ] Top 8 slate names paired tests and a single predicted winner (no hedging)

Notes

  • Mobile clients truncate around 30–40 characters — the strongest word should appear before that cut, not after
  • Subject and preview text are one unit: write them together so the pair reads as a complete pitch in the inbox
  • Curiosity and news-hook strategies tend to win for cold or growing lists; direct benefit and personal voice tend to win for loyal, high-affinity audiences
  • Recommended workflow: pick 2–3 lines from different strategies, A/B test on a send-time split, and log winners to build a house pattern over time

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

  • ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
  • <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

  1. Drag this file into a new chat, or copy and paste its contents
  2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills