Skip to content
Skill Authoring
Skill

/newsletter

Use this skill when the user says 'newsletter', 'email newsletter', 'weekly digest', 'subscriber growth', 'open rates', or needs subject lines, content structure, sponsorship placement, and growth tactics for email newsletters. Do NOT use for lead magnets or content pipelines.

BOOST
From plugin
memstack
42587 skills2 commands4 hooks
Install
$ npx -y skills add cwinvestments/memstack --skill newsletter --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/newsletter

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use this skill when the user says 'newsletter', 'email newsletter', 'weekly digest', 'subscriber growth', 'open rates', or needs subject lines, content structure, sponsorship placement, and growth tactics for email newsletters. Do NOT use for lead magnets or content pipelines.

SKILL.md

newsletter.SKILL.md
name: memstack-content-newsletter
description: "Use this skill when the user says 'newsletter', 'email newsletter', 'weekly digest', 'subscriber growth', 'open rates', or needs subject lines, content structure, sponsorship placement, and growth tactics for email newsletters. Do NOT use for lead magnets or content pipelines."
version: 1.0.0
license: "Proprietary, MemStack™ Pro by CW Affiliate Investments LLC. See LICENSE.txt"

Newsletter: Writing email newsletter edition...

*Produces an email newsletter edition with subject line formulas, section structure, personalization, link placement strategy, growth tactics, and engagement optimization.*

Activation

When this skill activates, output:

`Newsletter: Writing email newsletter edition...`

Then execute the protocol below.

Context Guard

| Context | Status | |---------|--------| | User says "newsletter", "email newsletter", "weekly digest" | ACTIVE | | User says "subscriber growth" or "open rates" | ACTIVE | | User wants to write a newsletter edition or start a newsletter | ACTIVE | | User wants a lead magnet with email capture | DORMANT: use Lead Magnet | | User wants a full content automation pipeline | DORMANT: use Content Pipeline |

Common Mistakes

| Mistake | Why It's Wrong | |---------|---------------| | "Newsletter = company updates" | Nobody cares about your company news. Deliver value: insights, tips, curated content. | | "Generic subject line" | "[Company] Monthly Newsletter" gets 10% opens. Curiosity-driven subjects get 35%+. | | "No consistent format" | Readers want predictable value. A consistent structure builds habit and trust. | | "Too many links" | More than 3-5 links per section dilutes clicks. Feature one primary link prominently. | | "No growth strategy" | "Build it and they will come" doesn't work. Actively promote every issue. |

Protocol

Step 1: Gather Newsletter Requirements

If the user hasn't provided details, ask:

> 1. **Topic/niche**: what's the newsletter about? > 2. **Audience**: who reads it? (role, industry, experience level) > 3. **Frequency**: weekly, biweekly, or monthly? > 4. **Type**: curated links, original essays, tips, industry news, or mixed? > 5. **Current state**: new or existing? (subscriber count, open rates) > 6. **Monetization**: free, paid, or sponsored?

Step 2: Write the Subject Line

**Subject line formulas:**

| Formula | Template | Example | |---------|---------|---------| | **Curiosity gap** | [Topic]: The [thing] nobody talks about | "Pricing: The metric nobody tracks" | | **Numbered value** | [X] [things] to [outcome] this week | "5 tools to ship faster this week" | | **Question** | Why [common practice] [doesn't work / is wrong]? | "Why your landing page isn't converting?" | | **Personal** | I [did thing], here's what happened | "I quit meetings for a month" | | **Direct value** | How to [outcome] (in [constraint]) | "How to write copy that converts (in 20 min)" | | **Current event** | [Event/trend]: What it means for [audience] | "GPT-5: What it means for developers" |

**Subject line rules:**

  • 6-10 words (40-50 characters) for mobile display
  • No ALL CAPS, no spam triggers ("FREE", "ACT NOW", "!!!")
  • Preview text (first 90 characters of email) should complement, not repeat the subject
  • A/B test 2 subjects per send (most platforms support this)
  • Track open rates by subject formula, double down on what works

Step 3: Design Section Structure

**Newsletter format template:**

# [Newsletter Name]: [Edition Title or Number]

## Intro (2-3 sentences)
[Personal note, context for this edition, or a hook that frames the content]

---

## [Section 1: Primary Content] (60% of newsletter)
[Your main value: original insight, deep dive, or featured piece]
[Include one primary CTA link]

---

## [Section 2: Quick Hits / Curated] (25% of newsletter)
### [Item 1 title]
[1-2 sentence summary + link]

### [Item 2 title]
[1-2 sentence summary + link]

### [Item 3 title]
[1-2 sentence summary + link]

---

## [Section 3: Closer] (15% of newsletter)
[Personal sign-off, question for readers, or community highlight]

---

[Footer: Unsubscribe | Forward to a friend | [Social links]]

**Section type options (pick 2-4 per edition):**

| Section | Content | Purpose | |---------|---------|---------| | **Deep Dive** | Original essay or analysis (500-800 words) | Demonstrate expertise | | **Quick Hits** | 3-5 curated links with one-line summaries | Deliver breadth of value | | **Tool/Resource** | Featured tool with your take on it | Practical value | | **Tip of the Week** | One actionable tactic they can use today | Quick win | | **Community Spotlight** | Reader question, testimonial, or submission | Build community | | **Sponsor Section** | Sponsored content (clearly labeled) | Monetization | | **Poll/Question** | Ask readers something: drives replies | Engagement signal |

Step 4: Write the Edition

**Intro paragraph rules:**

  • 2-3 sentences maximum
  • Personal and conversational (not corporate)
  • Frames why THIS edition matters
  • Optional: reference a current event or reader feedback

**Body content rules:**

  • Write at an 8th-grade reading level (clear, accessible)
  • Use headers, bold, and bullet points for scannability
  • One idea per paragraph (3 sentences max)
  • Link text should describe the destination ("Read the full case study" not "Click here")
  • Primary CTA should appear within the first scroll (above 300 words)

**Personalization techniques:**

| Technique | Implementation | Impact | |----------|---------------|--------| | First name in subject | "Hey {first_name}, [subject]" | +10-15% open rate | | Segment by interest | Tag subscribers → send relevant content | +20-30% click rate | | Reference past behavior | "Since you read about [topic]..." | Higher engagement | | Reader-submitted content | Feature reader questions or wins | Community loyalty |

Step 5: Link Placement Strategy

**Link placement hierarchy:**

| Position | Purpose |

Read more
Ships withmemstack

The structured skill framework for Claude Code: 131 professional skills for deployment, security, databases, content, marketing, and more. Skills activate automatically when you need them. Say "deploy this to Railway" and the right skill loads on demand.

Get the whole plugin

Other skills on memstack.