Newsletter forge
SkillForge — production-ready Claude & Claude Code skills for developers, knowledge workers, and marketers. 9 free skills (MIT) + a Pro pack.
npx -y skills add moses607/skillforge --skill newsletter-forgeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.2 KB, as published. Nobody here has run it
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
- Subject line — curiosity or value, ≤50 chars, no clickbait you can't cash. Give 3 options.
- Preview text — the ~90 chars after the subject in the inbox. Extend the subject, don't repeat it.
- 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!".
- One big idea — the issue is about one thing. Develop it: setup → insight → why it matters to the reader.
- Scannable body — short paragraphs, subheads if long, bold sparingly for the one line that matters. Assume skimming.
- One CTA — a single action (reply, click, try, share). Multiple CTAs split attention and lower every click.
- 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, not "everyone". "You" singular.
- The open must not be a warm-up; delete any first line that could be cut without loss.
- One CTA. If the user insists on two, make one clearly primary and one a low-key P.S.
- Match the sender's voice if samples are given; otherwise default to plain, warm, direct.