power-user-cultivation

Name: power-user-cultivation
Author: jonathimer

65installs6forks

How to install power-user-cultivation?

jonathimer/devmarketing-skills/power-user-cultivation

$npx -y skills add jonathimer/devmarketing-skills --skill power-user-cultivation

Installs into the current project.

Summary

When the user wants to identify and nurture developer advocates, build champion programs, or turn active users into contributors and evangelists. Trigger phrases include "power users," "developer advocates," "ambassador program," "champion program," "community contributors," "ref

Files · 1

View on GitHub

SKILL.md

1	# Power User Cultivation
2
3	This skill helps you identify your most engaged developers and turn them into advocates, contributors, and champions. No forced evangelism — just creating genuine value for developers who already love what you're building.
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 where your developers hang out and what motivates them is essential
13
14	2. Gather your data:
15	- Usage metrics by user
16	- Community participation data
17	- Support interactions (helpful answers, feature requests)
18	- Content created about your product
19	- Referral/invitation history
20
21	---
22
23	## The Power User Spectrum
24
25	Not all engaged users want the same relationship:
26
27	\| Level \| Behavior \| What They Want \| Your Response \|
28	\|-------\|----------\|----------------\|---------------\|
29	\| Active User \| Uses product regularly \| Product to keep working \| Keep shipping \|
30	\| Engaged User \| Participates in community \| Help and recognition \| Respond quickly \|
31	\| Advocate \| Recommends you unprompted \| Insider access \| Early access, direct line \|
32	\| Champion \| Creates content, answers questions \| Platform and recognition \| Formal program \|
33	\| Contributor \| Contributes code, docs, extensions \| Impact and ownership \| Contributor program \|
34
35	Key insight: Don't try to push everyone up the spectrum. Meet developers where they are. Some just want a great product — that's fine.
36
37	---
38
39	## Identifying Potential Advocates
40
41	### Behavioral Signals
42
43	Look for these patterns in your data:
44
45	Usage-based signals:
46	```
47	- Top 10% by API calls or usage
48	- Using advanced/power features
49	- Long tenure (>6 months active)
50	- Multiple projects using your product
51	- Early adopter of new features
52	```
53
54	Community signals:
55	```
56	- Answers questions from other users
57	- Files detailed, constructive bug reports
58	- Requests features thoughtfully
59	- Active in Discord/Slack/forums
60	- Mentions you positively on social
61	```
62
63	Content signals:
64	```
65	- Wrote blog post about your product
66	- Created tutorial or video
67	- Open sourced integration or extension
68	- Conference talk mentioning you
69	- Stack Overflow answers recommending you
70	```
71
72	### Social Listening for Discovery
73
74	Set up monitoring for:
75
76	1. Positive mentions:
77	- People recommending your product
78	- Success stories shared publicly
79	- "Just shipped with [your product]" posts
80
81	2. Content creators:
82	- Blog posts about your product
83	- Tutorial videos
84	- Conference talk announcements
85
86	3. Community helpers:
87	- People answering questions about you
88	- Defending your product in discussions
89	- Sharing tips and tricks
90
91	### Building a Power User List
92
93	Create a simple tracker:
94
95	\| Name \| Company \| Signals \| Score \| Status \|
96	\|------\|---------\|---------\|-------\|--------\|
97	\| @jane \| Startup X \| Top usage, wrote blog post, answers Qs \| 92 \| Champion candidate \|
98	\| @john \| Agency Y \| Heavy usage, feature requests \| 65 \| Engaged user \|
99	\| @sam \| Corp Z \| Multiple repos using product \| 58 \| Advocate candidate \|
100
101	Score calculation:
102	- Usage in top 10%: +20
103	- Community active: +15
104	- Created content: +25
105	- Answers others' questions: +20
106	- Positive social mentions: +10
107	- Feature requests accepted: +10
108
109	---
110
111	## Ambassador / Champion Programs
112
113	### Program Design
114
115	Tiered vs flat structure:
116
117	\| Structure \| Best For \| Pros \| Cons \|
118	\|-----------\|----------\|------\|------\|
119	\| Tiered (Bronze/Silver/Gold) \| Large communities \| Clear progression \| Can feel corporate \|
120	\| Flat (all equal) \| Small communities \| Simple, egalitarian \| Less motivation \|
121	\| Invite-only \| Premium feeling \| Exclusive, high quality \| Scaling issues \|
122	\| Application-based \| Qualifying interest \| Self-selected engaged users \| Rejection handling \|
123
124	Recommended: Start invite-only and small. Expand once you understand what works.
125
126	### Benefits That Developers Value
127
128	Do offer:
129
130	\| Benefit \| Why It Works \|
131	\|---------\|--------------\|
132	\| Early access to features \| Insider feeling, first to know \|
133	\| Direct line to team \| Skip support queue, real influence \|
134	\| Conference ticket sponsorship \| Tangible value, networking \|
135	\| Exclusive swag \| Quality items, not junk \|
136	\| Public recognition \| Build their personal brand \|
137	\| Reference/recommendation \| Career value \|
138	\| AWS/GCP credits \| Tangible value for projects \|
139	\| Contributor credits \| Public attribution \|
140
141	Don't offer:
142
143	\| Benefit \| Why It Fails \|
144	\|---------\|--------------\|
145	\| Mandatory content quotas \| Feels like work \|
146	\| Heavy NDA restr

People who liked this also viewed

6 picks

Type

power-user-cultivation

65installs6forks

View on GitHub

How to install power-user-cultivation?

jonathimer/devmarketing-skills/power-user-cultivation

$npx -y skills add jonathimer/devmarketing-skills --skill power-user-cultivation

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Power User Cultivation
2
3	This skill helps you identify your most engaged developers and turn them into advocates, contributors, and champions. No forced evangelism — just creating genuine value for developers who already love what you're building.
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 where your developers hang out and what motivates them is essential
13
14	2. Gather your data:
15	- Usage metrics by user
16	- Community participation data
17	- Support interactions (helpful answers, feature requests)
18	- Content created about your product
19	- Referral/invitation history
20
21	---
22
23	## The Power User Spectrum
24
25	Not all engaged users want the same relationship:
26
27	\| Level \| Behavior \| What They Want \| Your Response \|
28	\|-------\|----------\|----------------\|---------------\|
29	\| Active User \| Uses product regularly \| Product to keep working \| Keep shipping \|
30	\| Engaged User \| Participates in community \| Help and recognition \| Respond quickly \|
31	\| Advocate \| Recommends you unprompted \| Insider access \| Early access, direct line \|
32	\| Champion \| Creates content, answers questions \| Platform and recognition \| Formal program \|
33	\| Contributor \| Contributes code, docs, extensions \| Impact and ownership \| Contributor program \|
34
35	Key insight: Don't try to push everyone up the spectrum. Meet developers where they are. Some just want a great product — that's fine.
36
37	---
38
39	## Identifying Potential Advocates
40
41	### Behavioral Signals
42
43	Look for these patterns in your data:
44
45	Usage-based signals:
46	```
47	- Top 10% by API calls or usage
48	- Using advanced/power features
49	- Long tenure (>6 months active)
50	- Multiple projects using your product
51	- Early adopter of new features
52	```
53
54	Community signals:
55	```
56	- Answers questions from other users
57	- Files detailed, constructive bug reports
58	- Requests features thoughtfully
59	- Active in Discord/Slack/forums
60	- Mentions you positively on social
61	```
62
63	Content signals:
64	```
65	- Wrote blog post about your product
66	- Created tutorial or video
67	- Open sourced integration or extension
68	- Conference talk mentioning you
69	- Stack Overflow answers recommending you
70	```
71
72	### Social Listening for Discovery
73
74	Set up monitoring for:
75
76	1. Positive mentions:
77	- People recommending your product
78	- Success stories shared publicly
79	- "Just shipped with [your product]" posts
80
81	2. Content creators:
82	- Blog posts about your product
83	- Tutorial videos
84	- Conference talk announcements
85
86	3. Community helpers:
87	- People answering questions about you
88	- Defending your product in discussions
89	- Sharing tips and tricks
90
91	### Building a Power User List
92
93	Create a simple tracker:
94
95	\| Name \| Company \| Signals \| Score \| Status \|
96	\|------\|---------\|---------\|-------\|--------\|
97	\| @jane \| Startup X \| Top usage, wrote blog post, answers Qs \| 92 \| Champion candidate \|
98	\| @john \| Agency Y \| Heavy usage, feature requests \| 65 \| Engaged user \|
99	\| @sam \| Corp Z \| Multiple repos using product \| 58 \| Advocate candidate \|
100
101	Score calculation:
102	- Usage in top 10%: +20
103	- Community active: +15
104	- Created content: +25
105	- Answers others' questions: +20
106	- Positive social mentions: +10
107	- Feature requests accepted: +10
108
109	---
110
111	## Ambassador / Champion Programs
112
113	### Program Design
114
115	Tiered vs flat structure:
116
117	\| Structure \| Best For \| Pros \| Cons \|
118	\|-----------\|----------\|------\|------\|
119	\| Tiered (Bronze/Silver/Gold) \| Large communities \| Clear progression \| Can feel corporate \|
120	\| Flat (all equal) \| Small communities \| Simple, egalitarian \| Less motivation \|
121	\| Invite-only \| Premium feeling \| Exclusive, high quality \| Scaling issues \|
122	\| Application-based \| Qualifying interest \| Self-selected engaged users \| Rejection handling \|
123
124	Recommended: Start invite-only and small. Expand once you understand what works.
125
126	### Benefits That Developers Value
127
128	Do offer:
129
130	\| Benefit \| Why It Works \|
131	\|---------\|--------------\|
132	\| Early access to features \| Insider feeling, first to know \|
133	\| Direct line to team \| Skip support queue, real influence \|
134	\| Conference ticket sponsorship \| Tangible value, networking \|
135	\| Exclusive swag \| Quality items, not junk \|
136	\| Public recognition \| Build their personal brand \|
137	\| Reference/recommendation \| Career value \|
138	\| AWS/GCP credits \| Tangible value for projects \|
139	\| Contributor credits \| Public attribution \|
140
141	Don't offer:
142
143	\| Benefit \| Why It Fails \|
144	\|---------\|--------------\|
145	\| Mandatory content quotas \| Feels like work \|
146	\| Heavy NDA restr

People who liked this also viewed

6 picks

Type