github-demand

A research workflow for checking whether a product idea matches real demand on GitHub, a website where developers share code and discuss problems. It examines popular projects, growing issues, and repeated complaints.

In plain words
What is it for?
Use it to investigate product ideas, identify recurring developer problems, and recommend one focused first version. It produces a short conclusion, demand signals, user pains, and an MVP recommendation.
Why use it?
It replaces guesswork with evidence from current projects and user discussions. It helps separate a proven product category from a specific problem that is still unsolved.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/chenfei462/packsmith/github-demand
Any agent
npx skills add chenfei462/packsmith --skill github-demand
Clone the repo
git clone --depth 1 https://github.com/chenfei462/packsmith

Made for: Claude Code, Codex.

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 175 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00175
Opus 5 $0.00011 $0.00088
Sonnet 5 $0.00004 $0.00035
Haiku 4.5 $0.00002 $0.00017

Measured yesterday against content hash 1e56553286a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-demand scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

examples/research-launchpad/skills/github-demand/SKILL.md · 30 lines

What it actually says

GitHub Demand

Use this skill when a project idea needs evidence from GitHub rather than intuition.

Workflow

  1. Start from trending repos and topic pages.
  2. Look for repositories with strong star velocity or fast issue growth.
  3. Read open issues to identify repeated workflow pain.
  4. Separate category proof from unsolved workflow gaps.
  5. End with one narrow product recommendation, not a vague market map.

Output

  • one-sentence thesis
  • 3-5 demand signals
  • 2-3 user pains
  • one MVP recommendation

Rules

  • Prefer primary GitHub sources.
  • Include exact dates when calling something "latest" or "recent".
  • Distinguish evidence from inference.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 30 lines · 22 tokens per session scan A 1e56553286a0

Subscribe to this mod's changes

github-demand is a skill published in the GitHub repository chenfei462/packsmith (2 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 175 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

metrics-instrumentation

Specification for instrumenting an opik-backend workflow with operational OpenTelemetry metrics — per-stage throughput/latency/error counters and native histograms, dimensioned per-customer (workspace). Use when a pipeline (scoring, ingestion, experiments, jobs) needs per-stage visibility. Covers metric emission only…

comet-ml/opik · 93 tokens

swarms

Build agents and multi-agent systems with the Swarms framework — the Agent class, tools, autonomous loops, memory, and the 15+ multi-agent architectures (SequentialWorkflow, ConcurrentWorkflow, GraphWorkflow, HierarchicalSwarm, SwarmRouter, and more). Use whenever writing, reviewing, or debugging code that imports…

kyegomez/swarms · 73 tokens

happiness-skill

当用户问「怎么才能更幸福/为什么得到了还不满足/怎么减少焦虑」时调用。 核心理念: 幸福是缺憾感清空的默认状态, 是可训练的技能; 欲望是与自己的契约(得到前不快乐), 同时只留一个重大欲望; 活在当下。 不适用于: 临床抑郁等需要专业治疗的场景(本书方法不能替代医疗)。 Triggers: 幸福/不快乐/欲望/焦虑/知足/活在当下/happiness/desire/anxiety.

kangarooking/cangjie-skill · 136 tokens

short-drama-storyboard

把剧本和视觉事实转成有镜头职责、空间连续性和可冻结起点的 剧集/ /分镜.md。 每镜使用二级标题 ## SHOT-...,同镜下用 ### 冻结关键帧提示词 写起始帧正文。.

zenstory-ai/drama-skills · 102 tokens

seedance-prompt

This skill should be used when the user asks to write, improve, translate, compress, or debug a Seedance 2.0 video prompt; mentions T2V, I2V, V2V, R2V, camera direction, prompt quality, or provides reference assets for a production-ready prompt.

Emily2040/seedance-2.0 · 68 tokens

skill-curator

中文 Skill 收录评估器。用于核验 GitHub 上的 Claude Code、Codex、Agent Skills、Plugin、MCP、CLI 或 Agent 工作流是否值得加入精选列表;检查真实资产、安装方式、活跃度、重复项和安全边界,并生成分类、中文描述与可追溯证据。.

laolaoshiren/claude-code-skills-zh · 75 tokens