newsletter

Newsletter Skill

Most newsletters are forgettable. Subscribers open them once, skim the first paragraph, delete.

The newsletters that build loyal audiences—and businesses—do something different. They have a format readers can rely on. A voice that's recognizable. Content worth opening.

This skill helps you create newsletters people actually look forward to.

Read ./brand/ per _system/brand-memory.md

Follow all output formatting rules from _system/output-format.md

---

Brand Memory Integration

This skill reads brand context to ensure every newsletter edition sounds like the user's brand, speaks to their actual audience, and builds on what has worked before. It also checks the learnings journal for send-time data, subject line performance, and format preferences.

Reads: voice-profile.md, audience.md, learnings.md (all optional)

On invocation, check for ./brand/ and load available context:

1. Load voice-profile.md (if exists):

   • Match the brand's tone, vocabulary, and sentence rhythm in every section
   • Apply voice DNA to subject lines, hooks, body copy, and sign-offs
   • A "direct, proof-heavy" voice writes different newsletters than a "warm, story-driven" voice
   • Use vocabulary lists to stay on-brand: preferred words, banned words, signature phrases
   • Show: "Your voice is [tone summary]. Newsletter will match that register."

2. Load audience.md (if exists):

   • Know who is reading: their awareness level, sophistication, pain points, interests
   • Match content depth to audience sophistication (technical vs general, insider vs newcomer)
   • Use audience language in hooks and subject lines -- mirror how they talk
   • Inform content selection: what topics, what level of detail, what format they prefer
   • Show: "Writing for [audience summary]. Awareness: [level]."

3. Load learnings.md (if exists):

   • Check for send-time data (e.g., "Tuesday 7am outperforms Thursday 10am by 23%")
   • Check for subject line patterns that have worked or failed
   • Check for format preferences (long vs short, curated vs original)
   • Check for content topic performance data
   • Show: "Found [N] newsletter learnings. Applying: [key insight]."