Developer Newsletter

This skill helps you build and write newsletters that developers actually open, read, and look forward to receiving. Covers content strategy, writing, growth, and deliverability.

---

Before You Start

Load your audience context first. Read .agents/developer-audience-context.md to understand:

• Who you're writing for (role, seniority, tech stack)
• What content resonates (problems, interests)
• Where else they consume content (to avoid duplicate effort)
• Voice & tone (how casual/technical)

If the context file doesn't exist, run the developer-audience-context skill first.

---

Newsletter Strategy

Define Your Newsletter Type

Best practice: Pick ONE primary type. You can mix in others, but have a clear identity.

Frequency Matrix

Developer preference: Weekly is the sweet spot. Developers are busy and inbox-protective.

---

Content Mix Framework

The 70-20-10 Rule

Content Categories

Build a rotation of these:

---

Writing Developer Emails

Subject Line Framework

What works for developers:

What doesn't work:

Pre-header Text

The preview text after the subject line. Use it.

Email Structure

[Short personal intro - 1-2 sentences]

[Main content sections with clear headers]

[Code snippet if relevant]

[Quick links section]

[Sign-off with personality]

Code in Email

Code rendering is tricky in email. Options:

Recommendation: Keep code short. Use inline code for small snippets, link to full examples.

<pre style="background-color: #1e1e1e; color: #d4d4d4; padding: 16px; border-radius: 4px; font-family: 'Fira Code', monospace; font-size: 14px; overflow-x: auto;">
const result = await fetch('/api/data');
</pre>

---

Subject Line Testing

A/B Test Framework

Test one variable at a time:

Subject Line Checklist

Before sending:

• Under 50 characters (mobile preview)
• No spam trigger words (free, act now, limited time)
• Specific, not vague
• Matches email content (no bait and switch)
• Would YOU open this?

---

Growth Tactics

Organic Growth

Referral Programs

Cross-Promotion

Partner with complementary newsletters:

Swap mentions, not full ads.

---

Avoiding Spam Filters

Technical Setup

Content Hygiene

Red Flag Words

Avoid in subject lines and body:

---

Email Service Providers

Developer-Friendly Options

DIY Options

---

Metrics & Benchmarks

Key Metrics

What to Track

---

Newsletter Template

Subject: [Specific, benefit-driven headline]
Pre-header: [Teaser that complements subject]

---

Hey [first name],

[1-2 sentence personal intro or hook]

## [Main Section 1]

[2-3 paragraphs with value]

\`\`\`javascript
// Quick code example if relevant
\`\`\`

## [Main Section 2]

[Content]

## Quick Links

- [Link 1]: One-line description
- [Link 2]: One-line description
- [Link 3]: One-line description

## From the Community

[Highlight something from Discord/Twitter/GitHub]

---

[Personal sign-off]

[Name]

P.S. [Optional: extra CTA, fun fact, or teaser]

---

Tools

---

Related Skills

• developer-audience-context — Know who you're writing for
• devrel-content — Source content for your newsletter
• community-building — Generate community content
• developer-advocacy — Build your personal brand alongside newsletter

---

Supporting file: README.md

developer-newsletter

Build newsletters developers actually open.

What It Does

Guides you through creating and growing a developer newsletter. Covers content strategy, writing, subject lines, growth tactics, and avoiding spam filters.

When to Use

• Starting a developer newsletter
• Writing your next issue
• Improving open/click rates
• Growing your subscriber base
• When you say "newsletter," "email marketing," "dev newsletter," or "email list"

Quick Start

/developer-newsletter

I want to start a weekly newsletter about JavaScript performance.
Target: frontend developers at mid to senior level.

The skill will:

1. Load your developer audience context
2. Help define your newsletter type and frequency
3. Guide content mix and structure
4. Optimize subject lines and deliverability

Key Frameworks

Content Mix (70-20-10)

Subject Line Patterns

What works:

• Specific benefit: "Cut your build time by 40%"
• Technical curiosity: "The JavaScript feature nobody uses"
• Direct announcement: "v2.0 is here: async/await support"
• Number + topic: "7 TypeScript tricks senior devs use"

Benchmarks

Files

Included Guidance

• Frequency selection
• Subject line testing framework
• Code snippet formatting in email
• Spam filter avoidance
• Growth tactics (organic + referral)
• ESP comparison

Tools

• Octolens (https://octolens.com) — Find trending topics for newsletter content
• Buttondown/Beehiiv — Newsletter platforms
• SparkLoop — Referral programs
• Mail-Tester — Spam score checking

Related Skills

• developer-audience-context — Know your readers
• devrel-content — Source newsletter content
• community-building — Community-driven content ideas