$npx -y skills add ReScienceLab/opc-skills --skill requesthuntGenerate 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 Reque
| 1 | # RequestHunt Skill |
| 2 | |
| 3 | Generate user demand research reports by collecting and analyzing real user feedback from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. |
| 4 | |
| 5 | ## Prerequisites |
| 6 | |
| 7 | Install the CLI and authenticate: |
| 8 | ```bash |
| 9 | curl -fsSL https://requesthunt.com/cli | sh |
| 10 | requesthunt auth login |
| 11 | ``` |
| 12 | |
| 13 | The installer downloads a pre-built binary from [GitHub Releases](https://github.com/ReScienceLab/requesthunt-cli/releases) and verifies its SHA256 checksum before installation. Alternatively, build from source with `cargo install --path cli` from the [requesthunt-cli](https://github.com/ReScienceLab/requesthunt-cli) repository. |
| 14 | |
| 15 | The CLI displays a verification code and opens `https://requesthunt.com/device` — the human must enter the code to approve. Verify with: |
| 16 | ```bash |
| 17 | requesthunt config show |
| 18 | ``` |
| 19 | Expected output contains: `resolved_api_key:` with a masked key value (not `null`). |
| 20 | |
| 21 | For headless/CI environments, set the API key via environment variable (preferred): |
| 22 | ```bash |
| 23 | export REQUESTHUNT_API_KEY="$YOUR_KEY" |
| 24 | ``` |
| 25 | |
| 26 | Or save it to the local config file (created with owner-only permissions): |
| 27 | ```bash |
| 28 | requesthunt config set-key "$YOUR_KEY" |
| 29 | ``` |
| 30 | |
| 31 | Get your key from: https://requesthunt.com/dashboard |
| 32 | |
| 33 | > **Security**: Never hardcode API keys directly in skill instructions or agent output. Use environment variables or the secured config file. |
| 34 | |
| 35 | ## Output Modes |
| 36 | |
| 37 | Default output is TOON (Token-Oriented Object Notation) — structured and token-efficient. |
| 38 | Use `--json` for raw JSON or `--human` for table/key-value display. |
| 39 | |
| 40 | ## Platform Selection Guide |
| 41 | |
| 42 | Each platform captures different types of user feedback. Choose platforms based on the product category to maximize signal quality. |
| 43 | |
| 44 | ### Platform Strengths |
| 45 | |
| 46 | | Platform | Best For | Signal Type | Typical Yield | |
| 47 | |----------|----------|-------------|---------------| |
| 48 | | **YouTube** | Consumer products, hardware, lifestyle apps | Specific feature asks from review/tutorial comments | High (10-29 per topic) | |
| 49 | | **Reddit** | Developer tools, creator economy, niche communities | Deep technical discussions, long-tail needs | High for dev topics (up to 176) | |
| 50 | | **LinkedIn** | B2B software, healthcare, enterprise tools | Professional/industry opinions, market context | Low volume but high engagement | |
| 51 | | **X** | Trending topics, quick sentiment signals | Fragmented feedback, emotional reactions | Low-medium (1-6 per topic) | |
| 52 | | **GitHub** | Open-source tools, developer infrastructure | Concrete bugs and feature requests from issues | High for OSS, zero for non-tech | |
| 53 | | **Amazon** | Consumer products, electronics, home goods | Product review complaints and feature wishes | High for physical products | |
| 54 | |
| 55 | ### Recommended Platforms by Category |
| 56 | |
| 57 | | Category | Primary | Secondary | Notes | |
| 58 | |----------|---------|-----------|-------| |
| 59 | | **Automotive / Hardware** | YouTube | Amazon, Reddit | Video review comments + Amazon product reviews are richest sources | |
| 60 | | **Gaming / Entertainment** | YouTube | Amazon, Reddit | Game streams, product reviews, and community feedback | |
| 61 | | **Travel / Transportation** | YouTube | Amazon, LinkedIn | Travel vlogs + Amazon gear reviews + business travel needs | |
| 62 | | **Social / Communication** | YouTube | Reddit | App review videos + community discussions | |
| 63 | | **Food / Dining** | YouTube | Amazon, Reddit | Recipe/delivery app reviews + Amazon kitchen product feedback | |
| 64 | | **Real Estate / Home** | Amazon | YouTube, Reddit | Amazon dominates for home improvement and smart home products | |
| 65 | | **Education / Learning** | YouTube | Amazon | Tutorial video comments + Amazon course/book reviews | |
| 66 | | **Health / Medical** | LinkedIn | Amazon, X | Professional healthcare + Amazon health product reviews | |
| 67 | | **Creator Economy** | Reddit | GitHub | Reddit communities overwhelmingly active (Newsletter: 176 requests) | |
| 68 | | **Developer Tools** | Reddit | GitHub | Technical communities + open-source issue trackers | |
| 69 | | **AI / SaaS Products** | Reddit | LinkedIn | Reddit for user complaints, LinkedIn for industry analysis | |
| 70 | | **Consumer Electronics** | Amazon | YouTube, Reddit | Amazon product reviews are the primary signal source | |
| 71 | |
| 72 | ### Quick Selection Rules |
| 73 | |
| 74 | - **Consumer / hardware / lifestyle** → Amazon + YouTube first, Reddit second |
| 75 | - **Developer / creator tools** → Reddit first, GitHub second |
| 76 | - **B2B / enterprise / medical** → LinkedIn first, X second |
| 77 | - **Physical products / electronics** → Amazon first, YouTube second |
| 78 | - **Has open-source projects** → add GitHub |
| 79 | - **Everything** → add X as a supplementary source |
| 80 | |
| 81 | ## Research Workflow |
| 82 | |
| 83 | ### Step 1: Define Scope |
| 84 | |
| 85 | Before collecting data, clarify with the user: |
| 86 | 1. **Research Goal**: What domain/area to investigate? |
| 87 | 2. **Speci |