← ClaudeAtlas

newsletter-forgelisted

Draft an email newsletter issue built around one idea with a strong open and a single call to action. Use whenever the user asks to write a newsletter, an email issue, "this week's edition", a broadcast to subscribers, or wants to turn notes/links into a sendable email. Trigger even when they only give a rough topic or a pile of links to shape into an issue.
moses607/skillforge · ★ 0 · AI & Automation · score 68
Install: claude install-skill moses607/skillforge
# Newsletter Forge A newsletter earns the next open by being worth this one. Structure each issue around a single idea, open with a reason to keep reading, and ask for exactly one action. Sprawl kills open rates. ## Issue architecture 1. **Subject line** — curiosity or value, ≤50 chars, no clickbait you can't cash. Give 3 options. 2. **Preview text** — the ~90 chars after the subject in the inbox. Extend the subject, don't repeat it. 3. **Open** — first 1-2 sentences carry the whole email. A specific hook: a story beat, a sharp claim, a question the reader also has. No "Hope you're doing well!". 4. **One big idea** — the issue is *about* one thing. Develop it: setup → insight → why it matters to the reader. 5. **Scannable body** — short paragraphs, subheads if long, bold sparingly for the one line that matters. Assume skimming. 6. **One CTA** — a single action (reply, click, try, share). Multiple CTAs split attention and lower every click. 7. **Sign-off** — human, brief, optionally a P.S. (the P.S. is the second-most-read line — use it for the CTA or a hook to next issue). ## Output template ``` Subject options: 1. <...> 2. <...> 3. <...> Preview text: <...> --- <Open — the hook> <Body — the one idea, developed, scannable> **<CTA line>** → [link/action] <Sign-off> P.S. <optional — CTA reinforcement or teaser> ``` ## Rules - One idea per issue. If the user dumps five topics, pick the strongest and offer the rest as future issues — don't cram. - Write to one person