Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@contentstudio

Newsletter drafter

@contentstudio/newsletter-drafter

Draft this week's newsletter from your notes, links, and updates: one strong lead story, short sections, three subject line options with preview text, and a clear call to action. Keeps a consistent format issue to issue and never sends.

SkillContentv1.0.0 (latest)
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1---
  2. 2name: newsletter-drafter
  3. 3description: Draft an email newsletter issue from notes, links, product updates, or a past issue. Picks one lead story, writes short sections in a consistent format, offers three subject lines with preview text, and ends with one clear call to action. Use when the user says "draft the newsletter", "write this week's issue", "turn these links into a newsletter", "customer update email", or "monthly product update".
  4. 4license: MIT
  5. 5---
  6. 6
  7. 7# Newsletter drafter
  8. 8
  9. 9A newsletter people open is short, has one thing worth reading at the top, and looks the same every issue so readers know where to look. This kit drafts that from whatever the user has: a pile of links, release notes, or a messy brain dump.
  10. 10
  11. 11## When to use
  12. 12
  13. 13- Weekly or monthly newsletters, product update emails, community digests, investor or customer updates that go to a list.
  14. 14- "Draft the newsletter from these notes", "write issue 15", "monthly update email".
  15. 15- For one-off sales emails or event follow-ups, use `attendee-follow-up` or a sales kit instead.
  16. 16
  17. 17## Inputs
  18. 18
  19. 191. **Raw material:** notes, links with a line on why each matters, release notes, or a file in `content/`.
  20. 202. **Past issues:** look in `content/newsletter/` for the last two. Match their structure, length, and sign-off unless the user wants a change.
  21. 213. **Audience and goal:** who reads it, and the one action you want this issue (reply, book a demo, read a post, register for an event).
  22. 224. **Name and number** of the newsletter, and the sender.
  23. 235. **Voice:** `brand.md` if it exists.
  24. 24
  25. 25If there are no past issues, use the default structure below and say so.
  26. 26
  27. 27## Steps
  28. 28
  29. 291. **Pick the lead.** From the material, choose the single item the audience will care about most (not the one the company is proudest of). Say why in one line.
  30. 302. **Sort the rest** into at most 3 short sections. Cut anything that would need a paragraph of context. Put cuts in a "saved for next time" list.
  31. 313. **Write the lead:** headline under 10 words, 120 to 200 words, one concrete detail or number, ends with the link or action.
  32. 324. **Write the short sections:** 2 to 4 sentences each, a bold first phrase, one link each.
  33. 335. **One call to action**, near the end, as a single sentence plus a link or "just reply". Never three competing asks.
  34. 346. **Subject lines:** write three, each under 45 characters, in different styles (direct benefit, curiosity, number). Add preview text under 90 characters that adds to the subject, not repeats it. Recommend one.
  35. 357. **Read it as a skimmer:** headlines and bold phrases alone should tell the story. Total length under 450 words unless past issues run longer.
  36. 368. **Save** to `content/newsletter/<YYYY-MM-DD>-issue-<n>.md` and show it.
  37. 37
  38. 38## Default structure and output
  39. 39
  40. 40```markdown
  41. 41---
  42. 42subject_options:
  43. 43 - "Fewer no-shows, starting Monday" # recommended
  44. 44 - "The 2-line text that changed our week"
  45. 45 - "3 changes in this month's release"
  46. 46preview: "Plus a free reminder template and one question for you."
  47. 47---
  48. 48
  49. 49# <Newsletter name>, issue <n>
  50. 50
  51. 51Hi {{first_name}},
  52. 52
  53. 53## <Lead headline>
  54. 54<120 to 200 words. One detail. Link.>
  55. 55
  56. 56## Also this week
  57. 57**<Bold first phrase>.** <2 to 4 sentences.> <link>
  58. 58
  59. 59## One ask
  60. 60<One sentence and one link, or "Just reply and tell me...">
  61. 61
  62. 62<Sign-off as in past issues>
  63. 63
  64. 64---
  65. 65Saved for next time: <items cut>
  66. 66```
  67. 67
  68. 68## Guardrails
  69. 69
  70. 70- Never send, schedule, or upload to an email tool. Drafts only.
  71. 71- Do not invent numbers, customer names, quotes, or dates. Mark gaps as `<need: ...>`.
  72. 72- Keep merge fields in the format the user's email tool uses; ask if unsure, default `{{first_name}}`.
  73. 73- Always include the unsubscribe and address footer placeholders if past issues have them; never remove them.
Sign in to comment on a line