Company Radar
Varnan-Tech/opendirectory
Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.
Monitor what developers say about your brand, competitors, and the problems they're solving.
Install Developer Listening
$ npx skills add sickn33/agentic-awesome-skills --skill developer-listening -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-listening --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/developer-listening .claude/skills/developer-listening && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "developer-listening" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-listening into .claude/skills/developer-listening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-listening", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-listeningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill developer-listening -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-listening --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/developer-listening .agents/skills/developer-listening && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "developer-listening" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-listening into .agents/skills/developer-listening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-listening", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill developer-listening -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-listening --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/developer-listening .cursor/skills/developer-listening && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "developer-listening" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-listening into .cursor/skills/developer-listening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-listening", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/developer-listening--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill developer-listening -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-listening --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/developer-listening .gemini/skills/developer-listening && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "developer-listening" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-listening into .gemini/skills/developer-listening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-listening", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills developer-listeningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill developer-listening -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/developer-listening .github/skills/developer-listening && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "developer-listening" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-listening into .github/skills/developer-listening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-listening", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill developer-listening -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills developer-listening --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/developer-listening .opencode/skills/developer-listening && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "developer-listening" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/developer-listening into .opencode/skills/developer-listening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-listening", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
developer-listening- GitHub stars
- 47k
- Used in
- 1 other repo
- Token cost
- ~2.1k tokens
- SKILL.md length
- 956 words
- Files
- 2
- Skills in repo
- 1,394
- Repo updated
- First seen
- Licence
- MIT
At a glance
Monitor what developers say about your brand, competitors, and the problems they're solving.
- Works in 3 steps: Define Your Keyword Categories → Set Up Monitoring Tools → Platform-Specific Monitoring
- Tasks that involve Prioritization frameworks
- SKILL.md covers When to Use, Overview, Setting Up Your Monitoring… and Sentiment Analysis and…, plus 6 more sections
- Calls gh
What it does
Developer Listening is an agent skill from sickn33/agentic-awesome-skills. 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.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Marketing & SEO, covering Prioritization frameworks. It works with GitHub, X (Twitter), Discord and Reddit. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Tasks that involve Prioritization frameworks
Example prompts
- “/developer-listening”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Developer Listening loads about 2.1k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 956 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 956 words, ~2,119 tokens.
Download SKILL.mdSave it as
.claude/skills/developer-listening/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- 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 this skill when you need 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", "track...
Monitor developer conversations across platforms to understand sentiment, find engagement opportunities, and gather competitive intelligence.
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
Show full SKILL.md (396 more words)Show less
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
- Be helpful first, promotional second - Answer the question before mentioning your product
- Disclose affiliation - "I work at [company]" builds trust
- Match the platform culture - HN hates marketing speak, Reddit values authenticity
- Provide value even if they don't convert - Good advice builds reputation
- 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 issuesandgh search reposfor 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.
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/developer-listening of sickn33/agentic-awesome-skills.
- SKILL.md
- README.md
Open the folder on GitHubat commit 1e53ce2
Used in 1 other repository
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Developer Listening next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Developer Listening this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Company RadarVarnan-Tech/opendirectory | 672 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Wjs Promoting Skillsjianshuo/claude-skills | 130 | — | ~2k | Automated safety check: Pass | MIT | |
| Community Buildingmanojbajaj95/claude-gtm-plugin | 104 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Agent ReachOotto-AI/claude-content-skills | 101 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Auto Promotexiaotonng/pikiloom | 295 | — | ~629 | Automated safety check: Notes | MIT |
Similar skills
Wjs Promoting Skills
jianshuo/claude-skills
A skill your agent uses when the user wants to set up automated daily promotion / marketing for their Claude Code skills — researching how top skills are promoted on marketplaces (ClawHub / openclaw…
Community Building
manojbajaj95/claude-gtm-plugin
Build and grow online communities across all platforms and contexts — from developer/B2B communities (Discord, Slack, Circle, Discourse) to social communities (Twitter/X, Reddit, Farcaster) to…
Agent Reach
Ootto-AI/claude-content-skills
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g.
Auto Promote
xiaotonng/pikiloom
无人值守推广总入口。按 promo/orchestrate.md 跨所有启用渠道（GitHub / Twitter / Reddit）跑一轮：发现→去重→起草→自我批判→护栏→按 posture 发布→记录→度量。供每日 cron（schedule / loop）调用，也可手动运行。传 "post-approved" 只执行 batch 待发队列。
Octolens
sundial-org/awesome-openclaw-skills
Query and analyze brand mentions from Octolens API. An agent skill from sundial-org/awesome-openclaw-skills.
More from sickn33/agentic-awesome-skills
All 1,394 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Related
Works with
Questions about Developer Listening
What does Developer Listening do?
Monitor what developers say about your brand, competitors, and the problems they're solving. Developer Listening is an agent skill from sickn33/agentic-awesome-skills. Monitor what developers say about your brand, competitors, and the problems they're solving.
When should I use Developer Listening?
Developer Listening fits situations like: tasks that involve Prioritization frameworks.
How do I install Developer Listening in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill developer-listening -a claude-code`. Or copy the skill folder (skills/developer-listening in sickn33/agentic-awesome-skills) into .claude/skills/developer-listening in your project. Claude Code loads it when a task matches its description.
How do I install Developer Listening in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill developer-listening -a codex`. Or copy the skill folder (skills/developer-listening in sickn33/agentic-awesome-skills) into .agents/skills/developer-listening in your project. Codex loads it when a task matches its description.
Can I use Developer Listening in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill developer-listening -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developer-listening, .gemini/skills/developer-listening, .github/skills/developer-listening and .opencode/skills/developer-listening in your project.
What does Developer Listening need to run?
Going by SKILL.md and its folder, Developer Listening needs the command-line tools its instructions call (gh).
Does Developer Listening access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Developer Listening safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Developer Listening use?
Developer Listening is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Developer Listening use?
About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Developer Listening?
Skills that share tags, products or a category with Developer Listening: Company Radar (Varnan-Tech/opendirectory, 672 stars), Wjs Promoting Skills (jianshuo/claude-skills, 130 stars), Community Building (manojbajaj95/claude-gtm-plugin, 104 stars) and Agent Reach (Ootto-AI/claude-content-skills, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Developer Listening?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.