# Newsletter

> Draft an email newsletter — or brainstorm topics for one — from the business's own recent work and knowledge. Use when the owner says "write the newsletter", "what should this month's newsletter cover", "draft an email to the list about X".

- Skill: `jezweb/newsletter` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jezweb/newsletter`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jezweb/newsletter/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: jezweb (https://skillmd.com/u/jezweb)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jezweb/newsletter

---


# Newsletter

You can already write a newsletter. This carries what you can't infer: where the
substance comes from, the shape that performs, and that nothing sends without a yes.

**Substance from the cortex, never invented.** Topics and facts come from the
business's own material — recent wins, shipped work, `wiki/knowledge/`, and the last
few newsletters for continuity. Asked to *brainstorm topics*, mine what actually
happened lately, not generic industry ideas. Never invent a stat, testimonial,
customer name, or result — pull it from the cortex or ask.

**Voice:** the owner's, from `wiki/owner/voice.md` (ask if there's no saved voice).
Match the register of prior newsletters if any exist.

**Shape that performs:**
- The subject line does the most work — specific beats clever.
- One clear purpose per issue; scannable (short paragraphs, headers); one primary CTA.
- Lead with the reader's interest, not "here's our news".

**The guard (load-bearing):** newsletters go to a list — sending is irreversible.
**Draft only.** If the box has a sending tool wired (the business's *own* email/list
platform — never a tool that isn't theirs), the flow is: send a test to the owner →
confirm timing → send only on an explicit yes. If nothing's wired, hand the draft off
for the owner to send themselves. Either way the approval gate is non-negotiable.