Developer Relations Consultant
What it does
Audit the health, adoption, and documentation quality of a software package to determine its viability for production or its standing in the market. It bridges the gap between raw technical documentation and real-world developer sentiment by aggregating quantitative data from GitHub, StackOverflow, and Hacker News. Instead of just summarizing features, it provides a competitive analysis and identifies "documentation gaps"—specific scenarios where developers are likely to struggle because the current guides are insufficient. This is particularly useful when choosing between competing libraries or performing a gap analysis for a product you are currently maintaining.Use cases
- Tech Stack Evaluation: Comparing two competing frameworks to see which has better community support and a lower issue-to-resolution ratio.
- Documentation Auditing: Identifying exactly which technical scenarios are missing from your official docs based on common community pain points.
- Market Research: Tracking the growth trajectory of a package via download stats and star counts to gauge industry adoption.
- Due Diligence: Assessing the maintenance health of an open-source dependency before integrating it into an enterprise project.
How to use
Provide the name of the software package and a link to its documentation. The AI will then scan the web for repository metrics, community discussions, and competitor benchmarks to provide a professional engineering critique.markdown
I want you to act as a Developer Relations consultant. I will provide you with a software package and it's related documentation. Research the package and its available documentation, and if none can be found, reply "Unable to find docs". Your feedback needs to include quantitative analysis (using data from StackOverflow, Hacker News, and GitHub) of content like issues submitted, closed issues, number of stars on a repository, and overall StackOverflow activity. If there are areas that could be expanded on, include scenarios or contexts that should be added. Include specifics of the provided software packages like number of downloads, and related statistics over time. You should compare industrial competitors and the benefits or shortcomings when compared with the package. Approach this from the mindset of the professional opinion of software engineers. Review technical blogs and websites (such as TechCrunch.com or Crunchbase.com) and if data isn't available, reply "No data available".Tips
- Provide Direct Links: Give the AI the exact URL to the GitHub repo and the documentation site to reduce "hallucinations" and speed up the research process.
- Specify Competitors: If you have specific rivals in mind, list them. This forces the AI to do a side-by-side comparison rather than picking a random competitor.
- Ask for a "Scorecard": Request the output in a table format for the quantitative section to make the data easier to digest at a glance.
- Define the Target Audience: Tell the AI if the "professional opinion" should be from the perspective of a Senior Architect or a Junior Dev to shift the tone of the documentation gap analysis.
Notes
- Real-time Data Lag: Depending on the AI model's browsing capabilities, some very recent statistics (like downloads from the last 24 hours) may be slightly outdated.
- Private Repos: This skill only works for public software; it cannot analyze private repositories or internal company documentation unless the text is pasted directly.