--- name: developer-listening description: "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." risk: critical source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-listening source_repo: jonathimer/devmarketing-skills source_type: community date_added: 2026-07-01 license: MIT license_source: https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE --- # Developer Listening ## When to Use Use when researching developer feedback, brand mentions or competitor conversations across the named platforms. Trigger phrases include "developer listening", "monitor developer conversations", and "track product mentions". Monitor developer conversations across platforms to understand sentiment, find engagement opportunities, and gather competitive intelligence. ## Access and engagement boundaries Use public or explicitly authorized community sources and permitted platform access. Server membership alone does not authorize exporting private conversations. Minimize retained usernames and personal data, record source/date/coverage, and treat inferred sentiment or buying intent as uncertain. Monitoring does not authorize posting replies, direct messages, joining communities, or setting recurring jobs; prepare drafts and obtain the applicable user instruction before those actions. ## Overview 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. Effective developer listening helps you: - Understand how developers perceive your product - Find frustrated users who need help (and might churn) - Discover engagement opportunities before competitors - Gather unfiltered product feedback - Track competitive positioning in real conversations - Identify content gaps and documentation issues ## Setting Up Your Monitoring Strategy ### 1. Define Your Keyword Categories Before setting up monitoring, organize keywords into categories: **Brand Keywords:** - Your product name and common misspellings - Your company name - Key team members' names (for attribution) - Your GitHub org/repos - Your Twitter handles **Competitor Keywords:** - Direct competitor names - Competitor product features - Competitor pricing/plan names **Problem Keywords:** - Pain points your product solves - Error messages you help with - Workflow descriptions ("deploy to kubernetes", "manage API keys") - "How do I..." phrases relevant to your space **Buy Intent Keywords:** - "[category] recommendation" - "best [tool type] for [use case]" - "looking for [solution]" - "alternative to [competitor]" - "[competitor] vs" ### 2. Set Up Monitoring Tools Choose a social listening tool that aggregates mentions across developer platforms (GitHub, Hacker News, Reddit, Stack Overflow, Twitter). **Recommended Keyword Structure:** - Create separate keywords for brand, competitors, and problem spaces - Use exact match for brand names to reduce noise - Use broader matching for problem keywords - Set up negative keywords to filter irrelevant mentions ### 3. Platform-Specific Monitoring **GitHub:** - Monitor issues mentioning your product in other repos - Track discussions in relevant GitHub Discussions - Watch for your product in awesome-lists and comparison repos - Monitor stars/forks of competitor repos for traction signals **Hacker News:** - High-signal but low-volume - Comments often contain detailed technical feedback - "Show HN" and "Ask HN" posts reveal developer needs - Threads about competitors are engagement opportunities **Reddit:** - r/programming, r/webdev, r/devops, r/selfhosted, etc. - Subreddit-specific cultures require tailored responses - Question threads are high-intent opportunities **Stack Overflow:** - Monitor tags related to your product category - Questions reveal documentation gaps - Answers from competitors show their positioning **Twitter/X:** - Real-time sentiment and virality - Developer influencer conversations - Conference and event discussions - Complaint threads often go viral **Discord:** - Harder to monitor but high-signal - Join relevant community servers manually - Look for integration opportunities with popular servers ## Sentiment Analysis and Prioritization ### Prioritization Framework Not all mentions deserve equal attention. Prioritize based on: **High Priority (Respond within hours):** - Negative sentiment from existing users - Direct questions about your product - Complaints going viral - Competitor comparisons where you're losing - Buy-intent signals from ideal customer profiles **Medium Priority (Respond within 24-48 hours):** - Neutral mentions seeking recommendations - Feature requests in public forums - Documentation confusion - Competitor criticism (potential switchers) **Low Priority (Monitor and aggregate):** - General industry discussions - Competitor praise (learn from it) - Historical mentions for trend analysis ### Sentiment Filtering Most monitoring tools offer sentiment filtering. Key queries to set up: - Negative sentiment mentions from the last 30 days - High-relevance mentions that haven't been engaged with yet - Platform-specific filters (Hacker News, Reddit, Twitter) ## Finding Engagement Opportunities ### Types of Engagement Opportunities **Frustrated Users:** - Complaining about your product = urgent support opportunity - Complaining about competitors = potential conversion - Complaining about the problem space = thought leadership opportunity **Questions and Recommendations:** - Direct questions about your product - "What tool should I use for X" threads - Comparison requests **Buy Intent Signals:** - "Looking for a [your category]" - "Evaluating [competitor] vs [competitor]" - "Need to migrate from [competitor]" - "Budget approved for [solution]" ### Engagement Best Practices 1. **Be helpful first, promotional second** - Answer the question before mentioning your product 2. **Disclose affiliation** - "I work at [company]" builds trust 3. **Match the platform culture** - HN hates marketing speak, Reddit values authenticity 4. **Provide value even if they don't convert** - Good advice builds reputation 5. **Don't argue with critics** - Acknowledge, fix if valid, move on ## Competitive Intelligence from Conversations ### What to Track **Competitor Mentions:** - Praise (what are they doing right?) - Criticism (opportunities for you) - Feature requests (what's missing?) - Churn signals ("migrating away from") **Positioning Shifts:** - How competitors describe themselves - Which use cases they emphasize - Pricing and packaging discussions **Community Sentiment:** - Overall vibe toward competitors - Developer trust levels - Support quality perception ### Extracting Insights Track trends over time using your monitoring tool's analytics: - Sentiment trends for competitors over 90 days - Mention volume comparison between your brand and top competitors - Platform breakdown (where are conversations happening?) ## Tools ### Social Listening Use a monitoring tool that tracks developer platforms. Key capabilities to look for: - Multi-platform coverage (GitHub, HN, Reddit, Stack Overflow, Twitter) - Sentiment analysis - Keyword alerts and filtering - Analytics and trend tracking ### Platform-Specific Tools **GitHub Search:** - Use `gh search issues` and `gh search repos` for GitHub-specific monitoring - Track issues mentioning your product in other repositories **Twitter/X Search:** - Advanced search operators for precise monitoring - Track specific accounts and hashtags - Tools like Typefully, TweetDeck, or Hootsuite for monitoring **Reddit:** - Native Reddit search with subreddit filters - Third-party tools like Syften or F5Bot for alerts ## Related Skills - **competitor-tracking** - Systematic competitor analysis beyond conversation monitoring - **alternatives-pages** - Convert competitive insights into comparison content - **community-engagement** - Best practices for responding to developer conversations ## Example **User request:** > Monitor what developers say about your brand, competitors, and the problems they're solving. ## Limitations - Use this skill only when the task clearly matches its upstream source and local project context. - Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes. - Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions. --- Source attribution: jonathimer/devmarketing-skills contributors, via Agentic Awesome Skills Original project: https://github.com/jonathimer/devmarketing-skills License: MIT + CC-BY-4.0 License information: https://creativecommons.org/licenses/by/4.0/ Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2026 Jonathan Reimer Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Dave AI resource metadata Creator / publisher: jonathimer/devmarketing-skills contributors, via Agentic Awesome Skills Original project: https://github.com/jonathimer/devmarketing-skills Attribution basis: Recorded upstream repository Fields of work: Development & Engineering Roles: Software Developer Specialties: Specialty not specified Tools: Tool not specified Country applicability: Country not specified Classification basis: Dave AI task classification from package title, description, and declared metadata Instruction SHA-256: d7a4a13aef6e21dbed0788b37fc89c23501c492a029c226478113a9a95f27a63 Metadata reviewed: 2026-10-27 This metadata supersedes earlier Dave AI catalog attribution. Original instruction and supporting files are preserved.