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.
Detected risks:
requesthunt is a skill that generates user-demand research reports by collecting and analyzing real user feedback — feature requests, complaints, and questions — from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. It solves the product-research problem of finding out what users actually want by scraping public discussion and review sources and distilling them into a structured Markdown report of top feature requests, pain points, and cross-platform signal comparisons.
The skill wraps the RequestHunt CLI. Its documented prerequisites install the CLI via an official install script and authenticate through a device-code flow (or an API key supplied via the REQUESTHUNT_API_KEY environment variable for headless/CI use, or a secured local config file). It includes explicit security guidance to never hardcode API keys in skill instructions or agent output, and it notes the installer verifies a SHA256 checksum of a pre-built binary (with a build-from-source alternative via cargo). The bulk of the skill is a platform-selection guide: a strengths table and category-to-platform recommendations (for example, Amazon plus YouTube for consumer hardware, Reddit plus GitHub for developer tools, LinkedIn for B2B/medical), followed by a research workflow of defining scope, running scrape/search/list commands, and generating a report. Default output is a token-efficient TOON format, with JSON and human-readable modes available.
It targets product managers, founders, and researchers doing demand research, competitive analysis, or market research. The main security consideration is that setup instructs piping a remote install script directly into a shell, a convenience pattern that carries supply-chain risk even though it is the tool's official installer and verifies a checksum; credential handling itself follows safe, standard practices.
It collects real user feedback (feature requests, complaints, questions) from Reddit, X, GitHub, YouTube, LinkedIn, and Amazon and turns it into a structured demand-research report covering top feature requests, pain points, and per-platform signal comparison.
The RequestHunt CLI must be installed and authenticated. Authentication uses a device-code login flow, or for headless/CI you supply an API key via the REQUESTHUNT_API_KEY environment variable or a secured local config file. An API key is obtained from the RequestHunt dashboard.
Use the platform-selection guide: for example consumer/hardware/lifestyle favors Amazon and YouTube, developer/creator tools favor Reddit and GitHub, and B2B/enterprise/medical favors LinkedIn. The workflow recommends choosing 2-3 platforms best suited to the product category.
The skill explicitly warns never to hardcode API keys in skill instructions or agent output and to use environment variables or the owner-only-permission config file instead. Keys are managed through the CLI's config or an environment variable.
Setup pipes a remote install script from the vendor's site directly into a shell, which is the tool's official installer and verifies the downloaded binary's SHA256 checksum, but curl-piped-to-shell installation is an inherent supply-chain risk. A build-from-source alternative via cargo is documented for those who prefer to avoid the piped installer.
Quick Setup:
.claude/skills/Repository
resciencelab/opc-skills