Gh Issue To Demand Signal

Description

Takes a competitor's public GitHub repo URL, fetches their open issues via the GitHub REST API, filters noise locally, clusters issues into 6 demand categories, computes a demand score per issue and per cluster, and outputs a ranked demand gap report with a GTM messaging brief. Use when asked to scan a competitor's GitHub issues, find what their users are begging for, turn GitHub complaints int...

What this skill does

1. 1Fetches up to 200 open issues from any public GitHub repo via the REST API, filtering out bots, PRs, and zero-engagement noise locally.
2. 2Scores every issue by +1 reactions and comment count, then clusters them into 6 demand categories: feature gaps, bugs, UX complaints, performance, missing integrations, and docs.
3. 3Flags 'ignored demand' issues — high-reaction, 6+ months old, no planned label — as your immediate opportunity window.
4. 4Produces a ranked demand gap report and a GTM messaging brief with positioning angles, outreach hooks, and headlines grounded in verbatim issue titles.

When to use

• You want to find what users are begging a competitor to fix before building your roadmap.
• You need verbatim buyer language from real complaints to write sharper positioning copy.
• You are preparing competitive battlecards and want evidence of specific feature gaps.
• You want outreach hooks grounded in exact phrases frustrated users are writing publicly.

Tools used

Frequently asked questions