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:
- Load your developer audience context
- Help define your newsletter type and frequency
- Guide content mix and structure
- Optimize subject lines and deliverability
Key Frameworks
Content Mix (70-20-10)
| Percentage | Content Type |
|---|---|
| 70% | Value content (teach, inform, help) |
| 20% | Product content (updates, features) |
| 10% | Promotional (CTAs, asks) |
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
| Metric | Target |
|---|---|
| Open rate | 30-50% |
| Click rate | 5-15% |
| Unsubscribe rate | <0.5% |
Files
| File | Description |
|---|---|
SKILL.md |
Full skill instructions with templates |
Included Guidance
- Frequency selection
- Subject line testing framework
- Code snippet formatting in email
- Spam filter avoidance
- Growth tactics (organic + referral)
- ESP comparison
Tools
- Octolens — 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 readersdevrel-content— Source newsletter contentcommunity-building— Community-driven content ideas