Github Demand Radar
Use when the user asks to analyze a GitHub repository's issues/PRs to identify high-value commercial demand opportunities. Triggers: 「扫issue」「扫PR」「找需求」「分析仓库」「找商业化点子」「独立开发者切入点」「需求雷达」「扫一下明星项目」「生成需求报告」. Outputs scored demand cards with JTBD analysis, RICE scoring, Ugly Workaround evidence, and fake-door probe drafts. Also works in PR scan mode (Phase 1B) to find rejected/stale PRs as market gap signals.
Install
npx skills add geekjourneyx/github-demand-radar --skill github-demand-radargit clone --depth 1 https://github.com/geekjourneyx/github-demand-radar.git /tmp/github-demand-radar
mkdir -p ~/.claude/skills
cp -r /tmp/github-demand-radar/. ~/.claude/skills/github-demand-radarPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# GitHub 需求雷达 ## 🎯 核心目标 你是一个顶级的**技术商业化产品专家**。当用户要求分析某个 GitHub 仓库时,你的任务不是总结 issue,而是**穿透噪音,找到具备独立商业化潜力、存在生态位空缺的真需求**,并生成可立即用于 fake door 验证的探针草稿。 ## 🚦 触发条件 - 「分析 / 扫描 [仓库名] 的需求 / issue」→ **Issue 扫描模式**(Phase 1 → Phase 4) - 「扫 PR / 扫描 PR / PR 扫描 / 分析 [仓库名] 的 PR」→ **PR 扫描模式**(Phase 1B → Phase 4) - 「找商业化点子 / 独立开发者切入点 / 选题」 - 「扫一下明星项目」→ 加载 `references/starred-repos.md`,依次分析 - 「找跨生态共振需求」→ 直接跳到 **Phase 5 生态雷达**,不抓新数据 - 「这个开源项目有什么值得做的周边工具」 - 「生成报告」→ 跳到 **Phase 4B/4C**,使用本次会话已完成的评审结果写入文件(仅在已完成 Phase 3 后可用) ## 🚫 硬性约束(任何时候都不得违反) 1. **绝不全量读取 issue/PR**:所有 `gh issue view`/`gh pr view` 调用必须带 `--jq` 截断,绝不输出原始全文 2. **绝不省略探针草稿**:RICE ≥ 50 的需求必须写入 `probes/` 文件,不可只输出报告 3. **绝不臆造数据**:所有 RICE 分数必须来自真实抓到的 reactions/comments 数值 4. **Token 安全阀**:候选超过 10 个时,先按 reactions 排序取 Top 10 进入深析 5. **巨无霸项目软警告**:Stars > 100k 的项目先输出:「⚠️ 该项目生态位已固化(stars > 100k),独立开发者切入空间有限。是否仍要继续?」等待确认后再继续 6. **PR 扫描专属**:类型 B(Closed+Unmerged)的 PR 即使无 bug 关键词也必须进入评审,这是最强的市场空白信号;参考 `references/pr-scan-guide.md` --- ## 🔄 核心工作流 ### Phase 0 — 历史注入(可选,仅当 reports/_index.jsonl 存在时执行)
Details
- Skill name
github-demand-radar- Repository
- geekjourneyx/github-demand-radar
- License
- MIT
- Repo updated
- 24 May 2026
FAQ
What does the Github Demand Radar skill do?
Use when the user asks to analyze a GitHub repository's issues/PRs to identify high-value commercial demand opportunities. Triggers: 「扫issue」「扫PR」「找需求」「分析仓库」「找商业化点子」「独立开发者切入点」「需求雷达」「扫一下明星项目」「生成需求报告」. Outputs scored demand cards with JTBD analysis, RICE scoring, Ugly Workaround evidence, and fake-door probe drafts. Also works in PR scan mode (Phase 1B) to find rejected/stale PRs as market gap signals.
How do I install the Github Demand Radar skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add geekjourneyx/github-demand-radar --skill github-demand-radar. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Github Demand Radar popular?
It lives in geekjourneyx/github-demand-radar, which has 16 GitHub stars and 4 forks.
Related skills
Address PR Review
15mnapoli/skill-address-pr-review
Look at the pull request review comments and address any issues raised.
Repo to Skill
19shuyhere/repo-to-skill
Generate an agent skill from a GitHub open-source repository. Use when asked to create a skill from a repo URL, turn a GitHub project into a usable skill, or generate skill files for a CLI/library/framework. Triggers on phrases like "create a skill from this repo", "make a skill for vllm", "turn this GitHub project into a skill", "generate a skill from repo". Also use when asked to "skillify" a tool or generate usage instructions from source code. Command usage — `/skill repo-to-skill <github-repo-url>`.
Build It
16DevOtts/build-it
Autonomous goal-to-DoD delivery orchestrator — the build stage of the *-it lifecycle ("plan-it plans it, build-it builds it"); formerly named fable-it. Hand it a goal and a numbered Definition of Done and it runs the whole job to completion, typically unattended, enforcing checkable gates (turn-end, claim, state-change, phase-boundary, delegation, and safe-parallel: interlock, worktree, integration), disk-backed run state, an evidence ledger that makes VERIFIED a lookup, a fresh-eyes verification pass, and an honest per-criterion report. Model-adaptive for Sonnet 5 and Opus 4.8; host-agnostic
Github Stars Curator
22Leexunhuan743/github-stars-curator
Organize starred GitHub repos into stable, clear lists: detect new stars, download READMEs into a local corpus, classify each repo against the taxonomy, and sync the approved mapping back to GitHub via gh. Use this when a user wants their starred repos sorted into lists, a recent batch of new stars filed incrementally, or their star-list taxonomy reviewed and refined. Do not use for general GitHub issue/PR management, repo code search, or bookmarking non-GitHub resources.
Recat Web
120xtbug/Recat
Automatically install and set up the Recat website from github.com/0xtbug/Recat, including prerequisites, dependencies, local password, findings folder, build, and server startup. Also use to repair or develop an existing Recat installation.
Oss Launch
16AnayDhawan/oss-launch
Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG, .gitignore, .github/ issue + PR templates, CI/CD). Also covers launch (GitHub metadata, badges, Show HN, Reddit, YouTube), release cadence (SemVer + CHANGELOG), and demo-GIF generation. Triggers on "open source this", "OSS checklist", "prep for launch", "make this repo public", "add a license / co
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.