developer-listening

Name: developer-listening
Author: jonathimer

80installs6forks

How to install developer-listening?

jonathimer/devmarketing-skills/developer-listening

$npx -y skills add jonathimer/devmarketing-skills --skill developer-listening

Installs into the current project.

Summary

Monitor what developers say about your brand, competitors, and the problems they're solving. Track mentions and conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter, and Discord. Trigger phrases: "developer listening", "monitor developer conversations", "trac

Files · 1

View on GitHub

SKILL.md

1	# Developer Listening
2
3	Monitor developer conversations across platforms to understand sentiment, find engagement opportunities, and gather competitive intelligence.
4
5	## Overview
6
7	Developer listening is the practice of systematically monitoring what developers say about your brand, competitors, and the problems your product solves. Unlike traditional social listening, developer listening requires monitoring technical platforms where developers actually spend time: GitHub, Hacker News, Reddit programming communities, Stack Overflow, Twitter/X, and Discord servers.
8
9	Effective developer listening helps you:
10	- Understand how developers perceive your product
11	- Find frustrated users who need help (and might churn)
12	- Discover engagement opportunities before competitors
13	- Gather unfiltered product feedback
14	- Track competitive positioning in real conversations
15	- Identify content gaps and documentation issues
16
17	## Setting Up Your Monitoring Strategy
18
19	### 1. Define Your Keyword Categories
20
21	Before setting up monitoring, organize keywords into categories:
22
23	Brand Keywords:
24	- Your product name and common misspellings
25	- Your company name
26	- Key team members' names (for attribution)
27	- Your GitHub org/repos
28	- Your Twitter handles
29
30	Competitor Keywords:
31	- Direct competitor names
32	- Competitor product features
33	- Competitor pricing/plan names
34
35	Problem Keywords:
36	- Pain points your product solves
37	- Error messages you help with
38	- Workflow descriptions ("deploy to kubernetes", "manage API keys")
39	- "How do I..." phrases relevant to your space
40
41	Buy Intent Keywords:
42	- "[category] recommendation"
43	- "best [tool type] for [use case]"
44	- "looking for [solution]"
45	- "alternative to [competitor]"
46	- "[competitor] vs"
47
48	### 2. Set Up Monitoring Tools
49
50	Choose a social listening tool that aggregates mentions across developer platforms (GitHub, Hacker News, Reddit, Stack Overflow, Twitter).
51
52	Recommended Keyword Structure:
53	- Create separate keywords for brand, competitors, and problem spaces
54	- Use exact match for brand names to reduce noise
55	- Use broader matching for problem keywords
56	- Set up negative keywords to filter irrelevant mentions
57
58	### 3. Platform-Specific Monitoring
59
60	GitHub:
61	- Monitor issues mentioning your product in other repos
62	- Track discussions in relevant GitHub Discussions
63	- Watch for your product in awesome-lists and comparison repos
64	- Monitor stars/forks of competitor repos for traction signals
65
66	Hacker News:
67	- High-signal but low-volume
68	- Comments often contain detailed technical feedback
69	- "Show HN" and "Ask HN" posts reveal developer needs
70	- Threads about competitors are engagement opportunities
71
72	Reddit:
73	- r/programming, r/webdev, r/devops, r/selfhosted, etc.
74	- Subreddit-specific cultures require tailored responses
75	- Question threads are high-intent opportunities
76
77	Stack Overflow:
78	- Monitor tags related to your product category
79	- Questions reveal documentation gaps
80	- Answers from competitors show their positioning
81
82	Twitter/X:
83	- Real-time sentiment and virality
84	- Developer influencer conversations
85	- Conference and event discussions
86	- Complaint threads often go viral
87
88	Discord:
89	- Harder to monitor but high-signal
90	- Join relevant community servers manually
91	- Look for integration opportunities with popular servers
92
93	## Sentiment Analysis and Prioritization
94
95	### Prioritization Framework
96
97	Not all mentions deserve equal attention. Prioritize based on:
98
99	High Priority (Respond within hours):
100	- Negative sentiment from existing users
101	- Direct questions about your product
102	- Complaints going viral
103	- Competitor comparisons where you're losing
104	- Buy-intent signals from ideal customer profiles
105
106	Medium Priority (Respond within 24-48 hours):
107	- Neutral mentions seeking recommendations
108	- Feature requests in public forums
109	- Documentation confusion
110	- Competitor criticism (potential switchers)
111
112	Low Priority (Monitor and aggregate):
113	- General industry discussions
114	- Competitor praise (learn from it)
115	- Historical mentions for trend analysis
116
117	### Sentiment Filtering
118
119	Most monitoring tools offer sentiment filtering. Key queries to set up:
120
121	- Negative sentiment mentions from the last 30 days
122	- High-relevance mentions that haven't been engaged with yet
123	- Platform-specific filters (Hacker News, Reddit, Twitter)
124
125	## Finding Engagement Opportunities
126
127	### Types of Engagement Opportunities
128
129	Frustrated Users:
130	- Complaining about your produ

People who liked this also viewed

6 picks

Type

developer-listening

80installs6forks

View on GitHub

How to install developer-listening?

jonathimer/devmarketing-skills/developer-listening

$npx -y skills add jonathimer/devmarketing-skills --skill developer-listening

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Developer Listening
2
3	Monitor developer conversations across platforms to understand sentiment, find engagement opportunities, and gather competitive intelligence.
4
5	## Overview
6
7	Developer listening is the practice of systematically monitoring what developers say about your brand, competitors, and the problems your product solves. Unlike traditional social listening, developer listening requires monitoring technical platforms where developers actually spend time: GitHub, Hacker News, Reddit programming communities, Stack Overflow, Twitter/X, and Discord servers.
8
9	Effective developer listening helps you:
10	- Understand how developers perceive your product
11	- Find frustrated users who need help (and might churn)
12	- Discover engagement opportunities before competitors
13	- Gather unfiltered product feedback
14	- Track competitive positioning in real conversations
15	- Identify content gaps and documentation issues
16
17	## Setting Up Your Monitoring Strategy
18
19	### 1. Define Your Keyword Categories
20
21	Before setting up monitoring, organize keywords into categories:
22
23	Brand Keywords:
24	- Your product name and common misspellings
25	- Your company name
26	- Key team members' names (for attribution)
27	- Your GitHub org/repos
28	- Your Twitter handles
29
30	Competitor Keywords:
31	- Direct competitor names
32	- Competitor product features
33	- Competitor pricing/plan names
34
35	Problem Keywords:
36	- Pain points your product solves
37	- Error messages you help with
38	- Workflow descriptions ("deploy to kubernetes", "manage API keys")
39	- "How do I..." phrases relevant to your space
40
41	Buy Intent Keywords:
42	- "[category] recommendation"
43	- "best [tool type] for [use case]"
44	- "looking for [solution]"
45	- "alternative to [competitor]"
46	- "[competitor] vs"
47
48	### 2. Set Up Monitoring Tools
49
50	Choose a social listening tool that aggregates mentions across developer platforms (GitHub, Hacker News, Reddit, Stack Overflow, Twitter).
51
52	Recommended Keyword Structure:
53	- Create separate keywords for brand, competitors, and problem spaces
54	- Use exact match for brand names to reduce noise
55	- Use broader matching for problem keywords
56	- Set up negative keywords to filter irrelevant mentions
57
58	### 3. Platform-Specific Monitoring
59
60	GitHub:
61	- Monitor issues mentioning your product in other repos
62	- Track discussions in relevant GitHub Discussions
63	- Watch for your product in awesome-lists and comparison repos
64	- Monitor stars/forks of competitor repos for traction signals
65
66	Hacker News:
67	- High-signal but low-volume
68	- Comments often contain detailed technical feedback
69	- "Show HN" and "Ask HN" posts reveal developer needs
70	- Threads about competitors are engagement opportunities
71
72	Reddit:
73	- r/programming, r/webdev, r/devops, r/selfhosted, etc.
74	- Subreddit-specific cultures require tailored responses
75	- Question threads are high-intent opportunities
76
77	Stack Overflow:
78	- Monitor tags related to your product category
79	- Questions reveal documentation gaps
80	- Answers from competitors show their positioning
81
82	Twitter/X:
83	- Real-time sentiment and virality
84	- Developer influencer conversations
85	- Conference and event discussions
86	- Complaint threads often go viral
87
88	Discord:
89	- Harder to monitor but high-signal
90	- Join relevant community servers manually
91	- Look for integration opportunities with popular servers
92
93	## Sentiment Analysis and Prioritization
94
95	### Prioritization Framework
96
97	Not all mentions deserve equal attention. Prioritize based on:
98
99	High Priority (Respond within hours):
100	- Negative sentiment from existing users
101	- Direct questions about your product
102	- Complaints going viral
103	- Competitor comparisons where you're losing
104	- Buy-intent signals from ideal customer profiles
105
106	Medium Priority (Respond within 24-48 hours):
107	- Neutral mentions seeking recommendations
108	- Feature requests in public forums
109	- Documentation confusion
110	- Competitor criticism (potential switchers)
111
112	Low Priority (Monitor and aggregate):
113	- General industry discussions
114	- Competitor praise (learn from it)
115	- Historical mentions for trend analysis
116
117	### Sentiment Filtering
118
119	Most monitoring tools offer sentiment filtering. Key queries to set up:
120
121	- Negative sentiment mentions from the last 30 days
122	- High-relevance mentions that haven't been engaged with yet
123	- Platform-specific filters (Hacker News, Reddit, Twitter)
124
125	## Finding Engagement Opportunities
126
127	### Types of Engagement Opportunities
128
129	Frustrated Users:
130	- Complaining about your produ

People who liked this also viewed

6 picks

Type