Newsletter ops

The channel you actually own

This lesson ends with a real issue of your actual newsletter shipped: assembled by a skill from the week's content, reviewed in the repo, pasted into your sending tool by you, sent by you. It earns its 45 minutes because this is the channel without an asterisk. Every social channel in this course has one: closed platforms, terms that shift, algorithm risk. The newsletter has none of them. You own the list, and nothing between you and the reader changes its rules quarterly. If the engine you're building has a center of gravity, it's here.

• What Claude produces: the issue body, assembled from the week's published pieces, the newsletter/ folders in your derivative sets, and your curated links.
• Plus the trimmings: three subject-line options and preview text, drafted against your voice file - you pick on send day.
• All of it voice-passed and lint-passed in the repo, where your tools live. Your sending tool receives a finished issue to paste in, not a draft to fix.

The weekly-issue assembly skill

The weekly issue is the most predictable piece of content you make, which makes it the most automatable. The raw material already exists in your repo: this week's published posts, the best derivatives, and a handful of curated links. Assembly is the job; the skill does it.

1. Define the issue template as a file: your sections in order - e.g. one main essay or excerpt, two or three shorts, curated links with one-line takes, a PS. The template is the contract.
2. Build the newsletter skill: it reads content/published/ for the week, the newsletter/ folders inside this week's derivative sets, and a curated-links file you maintain by hand.
3. It assembles a full issue draft into content/drafts/, then runs the voice pass - newsletters drift corporate faster than any other format because they feel official.
4. You review and edit in the repo, where your lint and voice tools live - not in the sending tool's editor.
5. On approval (you move it to approved/), the output is the final issue file: three subject options, preview text, and a body formatted so it pastes clean into whatever you send with.

Curation stays human, permanently. The one-line takes on links you found interesting are the most personal part of any newsletter, and readers can tell when they're generated. The skill assembles around your curation; it doesn't replace it.

A finished file, never a send

The folder gate has a twin here: the engine's job ends at a finished issue file, and a human carries it into the sending tool. A botched social post embarrasses you to whoever scrolls past; a botched newsletter lands in 10,000 inboxes and stays there.

This also keeps your sending tool's own safety net in play: its preview, its test send, its scheduled-send confirmation. The skill gets you to a finished issue; the send flow stays exactly as careful as it was before you automated anything.

Send day and the feedback loop

The human part of send day is short, and it's the same four moves every week. Ritualize them.

1. Paste the issue into your sending tool, send yourself its test email, and read it on your phone - email clients break formatting in ways the editor preview hides.
2. Check subject line and preview text as a pair; the skill drafts three subject options, you pick one.
3. Press send (or schedule) in your sending tool yourself.
4. Afterwards, log open and click rates as a performance note in published/ - issue subjects that worked feed the corpus like everything else.

Do this now

Sources and further reading

• Claude Code skills docs
• How Anthropic's marketing team uses Claude