GitHub Radar
Use this skill to turn GitHub momentum into builder judgment. The goal is not to summarize a leaderboard; it is to decide what is worth using, learning from, copying ethically, or ignoring.
Inputs
Accept any of:
- A GitHub Trending page or date.
- A list of repositories.
- A category such as "AI coding agents", "skills", "RAG", "developer tools", or "open source SaaS".
- A user goal, audience, or build constraint.
If the user gives no category, scan broadly and prioritize developer tools, AI workflows, agent infrastructure, and products that can be turned into small shippable projects.
Workflow
- Gather candidates from GitHub Trending, GitHub Explore, repo README files, release notes, issues, and project websites when available.
- Filter out projects whose only signal is novelty, gray-area access, security misuse, or platform-rule arbitrage.
- Score each serious candidate on:
- Pain intensity: Does it solve an annoying, frequent problem?
- Adoption signal: Stars today, total stars, contributors, issues, recent commits.
- Builder leverage: Can an indie builder make a smaller or more focused version?
- Workflow fit: Does it become a skill, template, CLI, MCP server, dashboard, or SaaS?
- Trust risk: Security, compliance, maintenance, dependency, data privacy.
- Group recommendations into:
- Worth using now.
- Worth studying or emulating.
- Worth avoiding for now.
- Convert the best opportunity into a concrete next build step.
Output Format
Use concise sections:
## Today's Signal
One sharp paragraph about what changed.
## Worth Watching
- repo: why it is hot, what pain it proves, and the caveat.
## Worth Using
- repo: best use case, maturity, setup cost, and risk.
## Worth Emulating
- direction: target audience, wedge, MVP, differentiation, risk.
## Avoid For Now
- repo/category: why the signal is weak or risky.
## Best Next Build
Name one concrete project, skill, workflow, or repo to create next.
Judgment Rules
- Prefer boring utility with adoption over flashy demos with unclear users.
- If a repo is hot because it bypasses costs or access rules, flag the fragility.
- If a repo is infrastructure, ask what smaller vertical version can exist.
- If a repo is a skill collection, identify which skill has the clearest install-worthy pain.
- Do not recommend copying brands, code, secrets, or restricted platform behavior.
Next Step
Feed the best opportunity from your radar report into trend-to-product to shape it into a differentiated product idea with MVP scope.
1---2name: github-radar3description: Use when scanning GitHub Trending, GitHub Explore, or hot repositories to identify useful tools, product opportunities, skill/workflow ideas, and hype traps for builders.4---56# GitHub Radar78Use this skill to turn GitHub momentum into builder judgment. The goal is not to summarize a leaderboard; it is to decide what is worth using, learning from, copying ethically, or ignoring.910## Inputs1112Accept any of:1314- A GitHub Trending page or date.15- A list of repositories.16- A category such as "AI coding agents", "skills", "RAG", "developer tools", or "open source SaaS".17- A user goal, audience, or build constraint.1819If the user gives no category, scan broadly and prioritize developer tools, AI workflows, agent infrastructure, and products that can be turned into small shippable projects.2021## Workflow22231. Gather candidates from GitHub Trending, GitHub Explore, repo README files, release notes, issues, and project websites when available.242. Filter out projects whose only signal is novelty, gray-area access, security misuse, or platform-rule arbitrage.253. Score each serious candidate on:26 - Pain intensity: Does it solve an annoying, frequent problem?27 - Adoption signal: Stars today, total stars, contributors, issues, recent commits.28 - Builder leverage: Can an indie builder make a smaller or more focused version?29 - Workflow fit: Does it become a skill, template, CLI, MCP server, dashboard, or SaaS?30 - Trust risk: Security, compliance, maintenance, dependency, data privacy.314. Group recommendations into:32 - Worth using now.33 - Worth studying or emulating.34 - Worth avoiding for now.355. Convert the best opportunity into a concrete next build step.3637## Output Format3839Use concise sections:4041```markdown42## Today's Signal4344One sharp paragraph about what changed.4546## Worth Watching4748- repo: why it is hot, what pain it proves, and the caveat.4950## Worth Using5152- repo: best use case, maturity, setup cost, and risk.5354## Worth Emulating5556- direction: target audience, wedge, MVP, differentiation, risk.5758## Avoid For Now5960- repo/category: why the signal is weak or risky.6162## Best Next Build6364Name one concrete project, skill, workflow, or repo to create next.65```6667## Judgment Rules6869- Prefer boring utility with adoption over flashy demos with unclear users.70- If a repo is hot because it bypasses costs or access rules, flag the fragility.71- If a repo is infrastructure, ask what smaller vertical version can exist.72- If a repo is a skill collection, identify which skill has the clearest install-worthy pain.73- Do not recommend copying brands, code, secrets, or restricted platform behavior.7475## Next Step7677Feed the best opportunity from your radar report into `trend-to-product` to shape it into a differentiated product idea with MVP scope.
aimonj0729-ai