developer-email-sequences

Name: developer-email-sequences
Author: jonathimer

70installs6forks

How to install developer-email-sequences?

jonathimer/devmarketing-skills/developer-email-sequences

$npx -y skills add jonathimer/devmarketing-skills --skill developer-email-sequences

Installs into the current project.

Summary

When the user wants to create email sequences for developers including onboarding, product updates, re-engagement, or changelog communications. Trigger phrases include "developer emails," "onboarding sequence," "email drip," "developer newsletter," "changelog email," "re-engageme

Files · 1

View on GitHub

SKILL.md

1	# Developer Email Sequences
2
3	This skill helps you craft email sequences that developers actually read. No spam, no fluff — just useful content delivered at the right frequency.
4
5	---
6
7	## Before You Start
8
9	1. Load your developer audience context:
10	- Check if `.agents/developer-audience-context.md` exists
11	- If not, run the `developer-audience-context` skill first
12	- Understanding your developers' tech stack, pain points, and communication preferences is essential for effective email
13
14	2. Audit existing emails:
15	- What emails are you currently sending?
16	- What are open rates, click rates, unsubscribe rates?
17	- Any feedback from developers about your emails?
18
19	---
20
21	## The Developer Email Reality
22
23	Developers are ruthless with email:
24
25	\| Behavior \| Implication \|
26	\|----------\|-------------\|
27	\| Preview pane scanning \| Subject line and first line are everything \|
28	\| Aggressive unsubscribing \| One irrelevant email = unsubscribe \|
29	\| Plain text preference \| Many prefer plain text over HTML \|
30	\| Code snippet love \| Useful code examples get clicked \|
31	\| Transactional trust \| They open receipts, not "newsletters" \|
32
33	Golden rule: Every email must provide immediate value or solve a problem.
34
35	---
36
37	## Email Sequence Types
38
39	### 1. Onboarding Sequence
40
41	Goal: Get developers to their first "Hello World" moment.
42
43	Timing:
44	- Email 1: Immediately after signup
45	- Email 2: 24 hours (if no activation)
46	- Email 3: 3 days (if no activation)
47	- Email 4: 7 days (if no activation)
48	- STOP if they activate
49
50	Structure:
51
52	\| Email \| Purpose \| Content \|
53	\|-------\|---------\|---------\|
54	\| Welcome \| Confirm signup, one clear CTA \| Link to quickstart, nothing else \|
55	\| First nudge \| Address common blockers \| "Here's where most devs get stuck..." \|
56	\| Value reminder \| Show what's possible \| Customer example or code snippet \|
57	\| Last chance \| Direct ask \| "Need help? Reply to this email" \|
58
59	Template: Welcome Email
60
61	```
62	Subject: Your API key is ready
63
64	Hey [NAME],
65
66	Your API key: [KEY]
67
68	Quickstart (2 minutes):
69	[LINK TO QUICKSTART]
70
71	That's it. Hit reply if you get stuck.
72
73	— [SENDER NAME]
74	```
75
76	Template: First Nudge
77
78	```
79	Subject: Quick question about your setup
80
81	Hey [NAME],
82
83	Noticed you haven't made your first API call yet.
84
85	Where'd you get stuck?
86
87	[ ] Didn't have time yet
88	[ ] Confused about authentication
89	[ ] Can't find the right SDK
90	[ ] Something else
91
92	Just reply — I read every response.
93
94	— [SENDER NAME]
95	```
96
97	### 2. Activation Sequence
98
99	Goal: Turn first-time users into regular users.
100
101	Trigger: After first successful API call or integration.
102
103	Timing:
104	- Email 1: Immediately after first success
105	- Email 2: 3 days later
106	- Email 3: 7 days later
107	- Email 4: 14 days later
108
109	Structure:
110
111	\| Email \| Purpose \| Content \|
112	\|-------\|---------\|---------\|
113	\| Celebration \| Acknowledge progress \| "Your first call worked!" \|
114	\| Next step \| Show natural progression \| "Most devs do X next..." \|
115	\| Deep feature \| Introduce advanced capability \| Tutorial or code example \|
116	\| Integration \| Suggest production use \| Case study or deployment guide \|
117
118	### 3. Changelog / Product Update Emails
119
120	Goal: Keep developers informed without overwhelming them.
121
122	Frequency: Weekly digest or per-release (never more than 2x/week).
123
124	Structure:
125
126	```markdown
127	Subject: [Product] v2.3 — Faster webhooks, TypeScript 5 support
128
129	What's new:
130
131	## Breaking changes (read first)
132	- Webhook signature algorithm changed (migration guide)
133
134	## New
135	- TypeScript 5.0 support
136	- Batch API for bulk operations
137
138	## Improved
139	- Webhook delivery 3x faster
140	- Better error messages for auth failures
141
142	## Fixed
143	- Memory leak in long-running connections
144
145	Full changelog: [LINK]
146
147	---
148
149	Need help upgrading? Reply or join #support in Discord.
150	```
151
152	Rules:
153	- Breaking changes ALWAYS at the top
154	- Code examples for new features
155	- Link to full changelog, don't dump everything in email
156	- No marketing fluff — just facts
157
158	### 4. Re-engagement Sequence
159
160	Goal: Win back developers who've gone quiet.
161
162	Trigger: No activity for 30/60/90 days.
163
164	Timing:
165	- Email 1: Day 30 of inactivity
166	- Email 2: Day 45
167	- Email 3: Day 60
168	- Email 4: Day 90 (sunset warning)
169
170	Structure:
171
172	\| Email \| Purpose \| Content \|
173	\|-------\|---------\|---------\|
174	\| Check-in \| Soft touch \| "Everything okay?" \|
175	\| What's new \| Show progress \| Recent features they missed \|
176	\| Direct ask \| Understand why \| Survey or reply request \|
177	\| Sunset \| Account warning \| "We'll pause your account..." \|
178
179	Template: Check-in
180
181	```
182	Subject: Did something break?
183
184	Hey [NAME],
185
186	Haven't seen you in a while.
187
188	Quick check:
189
190	- Did you run into a problem? (Reply and I'

People who liked this also viewed

6 picks

Type

developer-email-sequences

70installs6forks

View on GitHub

How to install developer-email-sequences?

jonathimer/devmarketing-skills/developer-email-sequences

$npx -y skills add jonathimer/devmarketing-skills --skill developer-email-sequences

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Developer Email Sequences
2
3	This skill helps you craft email sequences that developers actually read. No spam, no fluff — just useful content delivered at the right frequency.
4
5	---
6
7	## Before You Start
8
9	1. Load your developer audience context:
10	- Check if `.agents/developer-audience-context.md` exists
11	- If not, run the `developer-audience-context` skill first
12	- Understanding your developers' tech stack, pain points, and communication preferences is essential for effective email
13
14	2. Audit existing emails:
15	- What emails are you currently sending?
16	- What are open rates, click rates, unsubscribe rates?
17	- Any feedback from developers about your emails?
18
19	---
20
21	## The Developer Email Reality
22
23	Developers are ruthless with email:
24
25	\| Behavior \| Implication \|
26	\|----------\|-------------\|
27	\| Preview pane scanning \| Subject line and first line are everything \|
28	\| Aggressive unsubscribing \| One irrelevant email = unsubscribe \|
29	\| Plain text preference \| Many prefer plain text over HTML \|
30	\| Code snippet love \| Useful code examples get clicked \|
31	\| Transactional trust \| They open receipts, not "newsletters" \|
32
33	Golden rule: Every email must provide immediate value or solve a problem.
34
35	---
36
37	## Email Sequence Types
38
39	### 1. Onboarding Sequence
40
41	Goal: Get developers to their first "Hello World" moment.
42
43	Timing:
44	- Email 1: Immediately after signup
45	- Email 2: 24 hours (if no activation)
46	- Email 3: 3 days (if no activation)
47	- Email 4: 7 days (if no activation)
48	- STOP if they activate
49
50	Structure:
51
52	\| Email \| Purpose \| Content \|
53	\|-------\|---------\|---------\|
54	\| Welcome \| Confirm signup, one clear CTA \| Link to quickstart, nothing else \|
55	\| First nudge \| Address common blockers \| "Here's where most devs get stuck..." \|
56	\| Value reminder \| Show what's possible \| Customer example or code snippet \|
57	\| Last chance \| Direct ask \| "Need help? Reply to this email" \|
58
59	Template: Welcome Email
60
61	```
62	Subject: Your API key is ready
63
64	Hey [NAME],
65
66	Your API key: [KEY]
67
68	Quickstart (2 minutes):
69	[LINK TO QUICKSTART]
70
71	That's it. Hit reply if you get stuck.
72
73	— [SENDER NAME]
74	```
75
76	Template: First Nudge
77
78	```
79	Subject: Quick question about your setup
80
81	Hey [NAME],
82
83	Noticed you haven't made your first API call yet.
84
85	Where'd you get stuck?
86
87	[ ] Didn't have time yet
88	[ ] Confused about authentication
89	[ ] Can't find the right SDK
90	[ ] Something else
91
92	Just reply — I read every response.
93
94	— [SENDER NAME]
95	```
96
97	### 2. Activation Sequence
98
99	Goal: Turn first-time users into regular users.
100
101	Trigger: After first successful API call or integration.
102
103	Timing:
104	- Email 1: Immediately after first success
105	- Email 2: 3 days later
106	- Email 3: 7 days later
107	- Email 4: 14 days later
108
109	Structure:
110
111	\| Email \| Purpose \| Content \|
112	\|-------\|---------\|---------\|
113	\| Celebration \| Acknowledge progress \| "Your first call worked!" \|
114	\| Next step \| Show natural progression \| "Most devs do X next..." \|
115	\| Deep feature \| Introduce advanced capability \| Tutorial or code example \|
116	\| Integration \| Suggest production use \| Case study or deployment guide \|
117
118	### 3. Changelog / Product Update Emails
119
120	Goal: Keep developers informed without overwhelming them.
121
122	Frequency: Weekly digest or per-release (never more than 2x/week).
123
124	Structure:
125
126	```markdown
127	Subject: [Product] v2.3 — Faster webhooks, TypeScript 5 support
128
129	What's new:
130
131	## Breaking changes (read first)
132	- Webhook signature algorithm changed (migration guide)
133
134	## New
135	- TypeScript 5.0 support
136	- Batch API for bulk operations
137
138	## Improved
139	- Webhook delivery 3x faster
140	- Better error messages for auth failures
141
142	## Fixed
143	- Memory leak in long-running connections
144
145	Full changelog: [LINK]
146
147	---
148
149	Need help upgrading? Reply or join #support in Discord.
150	```
151
152	Rules:
153	- Breaking changes ALWAYS at the top
154	- Code examples for new features
155	- Link to full changelog, don't dump everything in email
156	- No marketing fluff — just facts
157
158	### 4. Re-engagement Sequence
159
160	Goal: Win back developers who've gone quiet.
161
162	Trigger: No activity for 30/60/90 days.
163
164	Timing:
165	- Email 1: Day 30 of inactivity
166	- Email 2: Day 45
167	- Email 3: Day 60
168	- Email 4: Day 90 (sunset warning)
169
170	Structure:
171
172	\| Email \| Purpose \| Content \|
173	\|-------\|---------\|---------\|
174	\| Check-in \| Soft touch \| "Everything okay?" \|
175	\| What's new \| Show progress \| Recent features they missed \|
176	\| Direct ask \| Understand why \| Survey or reply request \|
177	\| Sunset \| Account warning \| "We'll pause your account..." \|
178
179	Template: Check-in
180
181	```
182	Subject: Did something break?
183
184	Hey [NAME],
185
186	Haven't seen you in a while.
187
188	Quick check:
189
190	- Did you run into a problem? (Reply and I'

People who liked this also viewed

6 picks

Type