Skip to content
Back to skills

Newsletter Writer

ASecurity

Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Use this to draft or rewrite a newsletter or email, sharpen weak email copy, plan a newsletter's structure and cadence, write a sequence, or repurpose an issue into other formats. For automated lifecycle and SMS programs, use `lifecycle-messaging`.

  • 1,651 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 1, 2026
ai-agentsrustgo

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add cbrock84/headcount --skill newsletter-writer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Newsletter Writer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Newsletter Writer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cbrock84-newsletter-writer/badge)](https://www.skillsdirectory.com/skills/cbrock84-newsletter-writer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: newsletter-writer
description: Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Use this to draft or rewrite a newsletter or email, sharpen weak email copy, plan a newsletter's structure and cadence, write a sequence, or repurpose an issue into other formats. For automated lifecycle and SMS programs, use `lifecycle-messaging`.
---

# Newsletter writer

A newsletter is a standing invitation that can be withdrawn at any time. Every issue either renews
it or spends it.

## Decide the job before writing

One issue, one job: teach something, argue something, or sell something. Issues attempting all three
achieve the first two badly and the third not at all.

## Subject line and preview

They are read together and should not repeat each other — the preview extends the subject rather
than echoing it. Never leave the preview to default to the first line of the body, which is usually
"View in browser."

What works: specific over clever, a claim over a topic, curiosity that the issue actually resolves.
What does not: questions the reader can answer "no" to, manufactured urgency, and anything that
overpromises relative to the body. Overpromising buys one open and costs the next five.

## Opening

The first sentence decides whether the rest is read. Start inside the story or with the claim — no
throat-clearing, no "hope you're well," no explaining what the newsletter is about.

Cut your first paragraph after drafting. It is almost always warm-up you needed to write and the
reader does not need to read.

## Structure

Short paragraphs. One idea each. Enough white space that the issue looks readable before it is read
— people decide whether to read from the shape of the thing.

Signpost where the issue turns, so someone skimming still gets the argument. Most readers skim.

## Voice

The thing that makes a newsletter worth opening is that it sounds like a person. Specifically:

- **First-hand detail.** What you actually did, saw, or got wrong. This is the part nobody else can
  write, and the part most drafts leave out.
- **Opinions with a stance.** Balanced surveys of both sides are forgettable.
- **Varied rhythm.** Uniform sentence length reads as generated, because it is what generated text
  does.
- **Concrete nouns and real numbers** in place of abstractions.

Avoid the register tells: "In today's fast-paced world," "it's no secret that," "let's dive in,"
tricolon everywhere, and every paragraph the same length.

## Selling without spending trust

Earn the ask. When an issue sells, the value comes first and the pitch is clearly marked — readers
forgive a clear pitch and resent a disguised one.

One call to action per issue. Multiple asks split attention and reduce all of them.

## Getting replies

Replies are the strongest signal a newsletter is working, and they improve deliverability more than
any technical fix.

Ask one specific question, occasionally rather than every issue, and make it easy to answer in a
sentence. "What did I get wrong here?" outperforms "let me know your thoughts," which asks the
reader to do the work of deciding what to say.

Then reply to the replies. A newsletter where the author answers is a different product from one
where they do not, and readers tell each other about the first kind.

## Editing

Three passes, in order: **structure** (is the order right, is anything missing), **cut** (remove
what does not advance the argument), **read aloud** (anything you stumble over gets rewritten). The
read-aloud pass catches what silent reading never does.

## Repurposing

One issue contains several short-form posts, a talk track, and often a longer piece. Plan which
before writing, so the sections that should stand alone are written to.

## Sources

`references/sources.md` in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.

## Never

- Write a subject line the opening does not pay off. It buys one open and costs the next.
- Sell in an issue that gave nothing else. The trust spent is not recovered by the next good one.
- Send an offer to the whole list when it applies to part of it.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…