Generate user demand research reports from real user feedback. Scrape and analyze feature requests, complaints, and questions from Reddit, X, GitHub, YouTube, LinkedIn, and Amazon. Use when user wants to do demand research, find feature requests, analyze user demand, or run RequestHunt queries.
npx skills add https://github.com/ReScienceLab/opc-skills --skill requesthunt
Generate user demand research reports by collecting and analyzing real user feedback from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon.
Install the CLI and authenticate:
curl -fsSL https://requesthunt.com/cli | sh
requesthunt auth login
The installer downloads a pre-built binary from GitHub Releases and verifies its SHA256 checksum before installation. Alternatively, build from source with cargo install --path cli from the requesthunt-cli repository.
The CLI displays a verification code and opens https://requesthunt.com/device — the human must enter the code to approve. Verify with:
requesthunt config show
Expected output contains: resolved_api_key: with a masked key value (not null).
For headless/CI environments, set the API key via environment variable (preferred):
export REQUESTHUNT_API_KEY="$YOUR_KEY"
Or save it to the local config file (created with owner-only permissions):
requesthunt config set-key "$YOUR_KEY"
Get your key from: https://requesthunt.com/dashboard
> Security: Never hardcode API keys directly in skill instructions or agent output. Use environment variables or the secured config file.
Default output is TOON (Token-Oriented Object Notation) — structured and token-efficient.
Use --json for raw JSON or --human for table/key-value display.
Each platform captures different types of user feedback. Choose platforms based on the product category to maximize signal quality.
| Platform | Best For | Signal Type | Typical Yield |
|----------|----------|-------------|---------------|
| YouTube | Consumer products, hardware, lifestyle apps | Specific feature asks from review/tutorial comments | High (10-29 per topic) |
| Reddit | Developer tools, creator economy, niche communities | Deep technical discussions, long-tail needs | High for dev topics (up to 176) |
| LinkedIn | B2B software, healthcare, enterprise tools | Professional/industry opinions, market context | Low volume but high engagement |
| X | Trending topics, quick sentiment signals | Fragmented feedback, emotional reactions | Low-medium (1-6 per topic) |
| GitHub | Open-source tools, developer infrastructure | Concrete bugs and feature requests from issues | High for OSS, zero for non-tech |
| Amazon | Consumer products, electronics, home goods | Product review complaints and feature wishes | High for physical products |
| Category | Primary | Secondary | Notes |
|----------|---------|-----------|-------|
| Automotive / Hardware | YouTube | Amazon, Reddit | Video review comments + Amazon product reviews are richest sources |
| Gaming / Entertainment | YouTube | Amazon, Reddit | Game streams, product reviews, and community feedback |
| Travel / Transportation | YouTube | Amazon, LinkedIn | Travel vlogs + Amazon gear reviews + business travel needs |
| Social / Communication | YouTube | Reddit | App review videos + community discussions |
| Food / Dining | YouTube | Amazon, Reddit | Recipe/delivery app reviews + Amazon kitchen product feedback |
| Real Estate / Home | Amazon | YouTube, Reddit | Amazon dominates for home improvement and smart home products |
| Education / Learning | YouTube | Amazon | Tutorial video comments + Amazon course/book reviews |
| Health / Medical | LinkedIn | Amazon, X | Professional healthcare + Amazon health product reviews |
| Creator Economy | Reddit | GitHub | Reddit communities overwhelmingly active (Newsletter: 176 requests) |
| Developer Tools | Reddit | GitHub | Technical communities + open-source issue trackers |
| AI / SaaS Products | Reddit | LinkedIn | Reddit for user complaints, LinkedIn for industry analysis |
| Consumer Electronics | Amazon | YouTube, Reddit | Amazon product reviews are the primary signal source |
Before collecting data, clarify with the user:
Choose platforms strategically based on the category:
# Consumer hardware — YouTube-first strategy
requesthunt scrape start "smart home devices" --platforms youtube,reddit --depth 2
# Developer tools — Reddit-first strategy
requesthunt scrape start "code editors" --platforms reddit,github --depth 2
# B2B / enterprise — LinkedIn-first strategy
requesthunt scrape start "electronic health records" --platforms linkedin,x --depth 2
# Consumer products — Amazon-first strategy
requesthunt scrape start "wireless earbuds" --platforms amazon,youtube,reddit --depth 2
# Broad research — all platforms
requesthunt scrape start "AI coding assistants" --platforms reddit,x,github,youtube,linkedin,amazon --depth 2
# Search with expansion for more data
requesthunt search "dark mode" --expand --limit 50
# List requests filtered by topic
requesthunt list --topic "ai-tools" --limit 100
Analyze collected data and generate a structured Markdown report:
# [Topic] User Demand Research Report
## Overview
- Scope: ...
- Data Sources: Reddit (N), X (N), GitHub (N), YouTube (N), LinkedIn (N), Amazon (N)
- Platform Strategy: [why these platforms were chosen for this category]
- Time Range: ...
## Key Findings
### 1. Top Feature Requests
| Rank | Request | Platform | Votes | Representative Quote |
|------|---------|----------|-------|---------------------|
### 2. Pain Points Analysis
- **Pain Point A**: ...
- Sources: [which platforms surfaced this]
### 3. Platform Signal Comparison
| Insight | Reddit | YouTube | LinkedIn | X | GitHub | Amazon |
|---------|--------|---------|----------|---|--------|--------|
| Volume | ... | ... | ... | ... | ... | ... |
| Signal type | Technical | UX/Feature | Strategic | Sentiment | Bug/FR | Product |
### 4. Competitive Comparison (if specified)
| Feature | Product A | Product B | User Expectations |
### 5. Opportunities
- ...
## Methodology
Based on N real user feedbacks collected via RequestHunt from [platforms]...
Data returned by requesthunt search, list, and scrape commands originates from public user-generated content on external platforms. When processing this data:
requesthunt search "authentication" --limit 20
requesthunt search "oauth" --expand # With realtime expansion
requesthunt search "API rate limit" --expand --platforms reddit,x,youtube
requesthunt list --limit 20 # Recent requests
requesthunt list --topic "ai-tools" --limit 10 # By topic
requesthunt list --platforms reddit,github,youtube # By platform
requesthunt list --category "Developer Tools" # By category
requesthunt list --sort top --limit 20 # Top voted
requesthunt scrape start "developer-tools" --depth 1 # Default: all platforms
requesthunt scrape start "ai-assistant" --platforms reddit,x,github,youtube,linkedin,amazon --depth 2
requesthunt scrape status "job_123" # Check job status
requesthunt topics # List all topics by category
requesthunt usage # View account stats
requesthunt config show # Check auth status
requesthunt auth login) or manual API keyWeb search, content extraction, crawling, and research capabilities using Tavily API
Fetch Xiaohongshu (RedNote / xhs) user profile information and their published notes list by user ID, returning nickname, bio, follower/following counts, engagement totals, tags, and paginated notes with engagement stats. Use when user mentions user profile xiaohongshu, rednote creator profile, xhs influencer data, scrape xiaohongshu user, get blogger notes, xiaohongshu author info, KOL discovery xiaohongshu, rednote user stats, creator profile rednote, xiaohongshu blogger analysis, get xhs user followers, rednote influencer profile, xiaohongshu account info, xhs creator data, user notes list xiaohongshu, rednote account scrape, xiaohongshu KOL research.
Multi-engine web search (SearXNG) + browsing/scraping (Camofox, CloakBrowser). Use whenever you need to do web research.
> This skill should be used when performing web research beyond a simple single search -- looking into topics, comparing options, investigating questions, finding recommendations, or any task where effective use of Exa, Firecrawl, and Reddit tools matters. Triggers on "research", "look into", "investigate", "compare", "find out about", "search for", "find information", "what do people think about", "what are the best", "look up", or multi-source search tasks. Also invocable explicitly by deep-research team members via the Skill tool.
This skill should be used when the user requests to research topics using FireCrawl, enrich notes with web sources, search and scrape information, or write scientific/academic papers. It extracts research topics from markdown files, creates research documents with scraped sources, generates BibTeX bibliographies from research results, and provides Pandoc/MyST templates for academic writing with citation management.
Use this skill for web search, extraction, mapping, crawling, and research via Tavily’s REST API when web searches are needed and no built-in tool is available, or when Tavily’s LLM-friendly format is beneficial.
Web search, content extraction, crawling, and research capabilities using Tavily API. Use when you need to search the web for current information, extracting content from URLs, or crawling websites.
> AI citation readiness audit ONLY (does not touch Google rankings, use blog-rewrite for combined Google+AI work). Use whenever the user wants their content to rank in ChatGPT, Perplexity, Claude, Gemini, or Google AI Overviews. AI citation optimization audit scoring blog posts for ChatGPT, Perplexity, and Google AI Overview citability. Evaluates passage-level citability, Q&A formatting, entity clarity, structured data, and AI crawler accessibility. Generates citation capsules and a 0-100 AI Citation Readiness score. Use when user says "geo", "ai citation", "ai optimization", "citation audit", "aeo", "perplexity optimization", "chatgpt citation".
Take resciencelab/requesthunt from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference cargo, go.
Without those the skill loads but fails at the first command.