Sample output — this is sample output from the Newsletter Writer skill (showing the finished product). The full methodology, checklists, and all reference docs live in the paid skill. All brands, people, and data below are fictional.
HALF-CUP · A WEEKLY FOR INDEPENDENT CREATORS

Half-Cup

A weekly for independent creators: 3 tools, 1 method, 1 sentence worth stealing.
Issue #12October 8, 2026≈ 4 min readBy Sam Half-Cup
SUBJECT LINE
Write one newsletter issue in 90 minutes
Preview: plus 3 tools I'm actually using this week — and one number: 62%.
HEADNOTE

This week I deliberately took my own writing flow apart

On Tuesday night I screen-recorded my entire process of writing this issue — not to teach it, but to see where the time actually went. The results were a little embarrassing: 47 minutes went to "getting in the mood", only 38 minutes to actual writing, and the last 5 to fighting the layout.

So I ran an experiment: hard time-boxes for each stage — 10 minutes to pick a topic, 40 for the deep dive, 15 for tools, 25 to wrap up. Stop when the timer rings, finished or not. Guess what? The issue you're reading right now is the result: 88 minutes, one draft.

Time-boxing isn't a discipline performance — it kills the real enemy of newsletter writing: the open-ended "never quite done" feeling. Below is the full breakdown of the method, plus this week's three tools.

DEEP DIVE

The four time-boxes that finish an issue in 90 minutes

The core insight: an unfinished newsletter is almost never a writing problem — it's decisions with no deadlines. Every stage deserves a moment to be "sentenced".

Box 1: Pick a topic (10 minutes). Open your backlog list, circle one on first instinct, push everything else to next week. No comparing, no "let me think more". The cost of agonizing over a topic always exceeds the cost of picking the wrong one — because there's another issue next week.

Box 2: Deep dive (40 minutes). Answer only one question: "What will be different for the reader next Monday morning?" If you can't answer it, switch topics — don't force it. Thesis first: your judgment must appear in the first three sentences, evidence after. Target: 400–700 words, one idea fully unpacked.

Box 3: Tools & resources (15 minutes). Two lines per recommendation: what it is + your verdict (who it's for / when to skip). If you can't write a verdict, you haven't earned the right to recommend it — cut it.

Box 4: Wrap-up (25 minutes). Two subject-line candidates (for A/B testing), one line of preview copy, and exactly one call to action at the end. Then read it aloud; rewrite anywhere you stumble — your readers are reading this on the subway.

"Deadlines aren't the enemy — the absence of deadlines is."— This week's deep-dive takeaway

Monday's test is simple: set the four timers, check the total when you're done. If it's over 100 minutes, come back and tell me which box tripped you up — just reply to this email. I read every reply.

TOOLKIT

3 things I'm actually using this week

DATA POINT
62%
Of the 214 readers who answered last issue's survey, the share who say they're "always writing the night before send" — up from 31% in March (n=186). The last-minute scramble is becoming the norm, not the exception.
Source: Half-Cup reader survey (fictional data, for illustration only)
QUOTE

"You don't need another list of 47 tools — you need the three you'll actually open tomorrow morning."

— From this week's editor's note
CLOSER

See you next Thursday, same time, for Issue #13. The topic is set: the welcome email sequence — the 3 emails a new subscriber gets in their first 7 days decide whether they stay.

→ One small ask this week: reply to this email and tell me in one sentence — where does your time get stuck when you write?

I reply to every one. Really.