requesthunt

resciencelab/opc-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/resciencelab/opc-skills --skill requesthunt
0 commentsdiscussion
summary

Collect and analyze real user feedback from Reddit, X, and GitHub to generate demand research reports.

  • Scrapes feature requests, complaints, and questions across three platforms with filtering by topic, category, platform, and time range
  • Includes search with real-time expansion, topic browsing, and sorting by popularity to identify top user demands
  • Provides structured workflow from scope definition through data collection to formatted Markdown report generation
  • Rate-limited API wi
skill.md

RequestHunt Skill

Generate user demand research reports by collecting and analyzing real user feedback from Reddit, X (Twitter), and GitHub.

Prerequisites

Install the CLI and authenticate:

curl -fsSL https://requesthunt.com/cli | sh
requesthunt auth login

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, use a manual API key instead:

requesthunt config set-key rh_live_your_key

Get your key from: https://requesthunt.com/dashboard

Output Modes

Default output is TOON (Token-Oriented Object Notation) — structured and token-efficient. Use --json for raw JSON or --human for table/key-value display.

Research Workflow

Step 1: Define Scope

Before collecting data, clarify with the user:

  1. Research Goal: What domain/area to investigate? (e.g., AI coding assistants, project management tools)
  2. Specific Products: Any products/competitors to focus on? (e.g., Cursor, GitHub Copilot)
  3. Platform Preference: Which platforms to prioritize? (reddit, x, github)
  4. Time Range: How recent should the feedback be?
  5. Report Purpose: Product planning / competitive analysis / market research?

Step 2: Collect Data

# 1. Trigger realtime scrape for the topic
requesthunt scrape start "ai-coding-assistant" --platforms reddit,x,github --depth 2

# 2. Search with expansion for more data
requesthunt search "code completion" --expand --limit 50

# 3. List requests filtered by topic
requesthunt list --topic "ai-tools" --limit 100

Step 3: Generate Report

Analyze collected data and generate a structured Markdown report:

# [Topic] User Demand Research Report

## Overview
- Scope: ...
- Data Sources: Reddit (X), X (Y), GitHub (Z)
- Time Range: ...

## Key Findings

### 1. Top Feature Requests
| Rank | Request | Sources | Representative Quote |
|------|---------|---------|---------------------|

### 2. Pain Points Analysis
- **Pain Point A**: ...

### 3. Competitive Comparison (if specified)
| Feature | Product A | Product B | User Expectations |

### 4. Opportunities
- ...

## Methodology
Based on N real user feedbacks collected via RequestHunt...

Commands

Search

requesthunt search "authentication" --limit 20
requesthunt search "oauth" --expand                          # With realtime expansion
requesthunt search "API rate limit" --expand --platforms reddit,x

List

requesthunt list --limit 20                                  # Recent requests
requesthunt list --topic "ai-tools" --limit 10               # By topic
requesthunt list --platforms reddit,github                    # By platform
requesthunt list --category "Developer Tools"                # By category
requesthunt list --sort top --limit 20                       # Top voted

Scrape

requesthunt scrape start "developer-tools" --depth 1         # Default: all platforms
requesthunt scrape start "ai-assistant" --platforms reddit,x,github --depth 2
requesthunt scrape status "job_123"                          # Check job status

Reference

requesthunt topics                                           # List all topics by category
requesthunt usage                                            # View account stats
requesthunt config show                                      # Check auth status

API Info

how to use requesthunt

How to use requesthunt on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add requesthunt
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/resciencelab/opc-skills --skill requesthunt

The skills CLI fetches requesthunt from GitHub repository resciencelab/opc-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/requesthunt

Reload or restart Cursor to activate requesthunt. Access the skill through slash commands (e.g., /requesthunt) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.843 reviews
  • Daniel Singh· Dec 24, 2024

    Solid pick for teams standardizing on skills: requesthunt is focused, and the summary matches what you get after install.

  • Nia Choi· Dec 16, 2024

    requesthunt has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Shikha Mishra· Dec 4, 2024

    requesthunt reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Rahul Santra· Nov 23, 2024

    I recommend requesthunt for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Ishan White· Nov 11, 2024

    We added requesthunt from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Min Gill· Nov 11, 2024

    requesthunt is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Kwame Rao· Nov 7, 2024

    requesthunt fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Neel Liu· Oct 22, 2024

    We added requesthunt from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Pratham Ware· Oct 14, 2024

    Useful defaults in requesthunt — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kaira Rao· Oct 2, 2024

    requesthunt fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 43

1 / 5