producthunt

resciencelab/opc-skills · updated May 11, 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 producthunt
0 commentsdiscussion
summary

Search and retrieve Product Hunt posts, topics, users, and collections via GraphQL API.

  • Four command categories: posts (by slug/ID, featured, filtered by topic or date), topics (lookup and search), users (profile and post history), and collections (featured and by ID)
  • Requires a Product Hunt developer token set as PRODUCTHUNT_ACCESS_TOKEN environment variable
  • Rate limited to 6250 complexity points per 15 minutes; includes built-in scripts for quick validation and data retrieval
skill.md

ProductHunt Skill

Get posts, topics, users, and collections from Product Hunt via the official GraphQL API.

Prerequisites

Set access token in ~/.zshrc:

export PRODUCTHUNT_ACCESS_TOKEN="your_developer_token"

Get your token from: https://www.producthunt.com/v2/oauth/applications

Quick Check:

cd <skill_directory>
python3 scripts/get_posts.py --limit 3

Commands

All commands run from the skill directory.

Posts

python3 scripts/get_post.py chatgpt                    # Get post by slug
python3 scripts/get_post.py 12345                      # Get post by ID
python3 scripts/get_posts.py --limit 20                # Today's featured posts
python3 scripts/get_posts.py --topic ai --limit 10     # Posts in topic
python3 scripts/get_posts.py --after 2026-01-01        # Posts after date
python3 scripts/get_post_comments.py POST_ID --limit 20

Topics

python3 scripts/get_topic.py artificial-intelligence  # Get topic by slug
python3 scripts/get_topics.py --query "AI" --limit 20 # Search topics
python3 scripts/get_topics.py --limit 50              # Popular topics

Users

python3 scripts/get_user.py rrhoover                  # Get user by username
python3 scripts/get_user_posts.py rrhoover --limit 20 # User's posts

Collections

python3 scripts/get_collection.py SLUG_OR_ID          # Get collection
python3 scripts/get_collections.py --featured --limit 20

API Info

how to use producthunt

How to use producthunt 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 producthunt
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 producthunt

The skills CLI fetches producthunt 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/producthunt

Reload or restart Cursor to activate producthunt. Access the skill through slash commands (e.g., /producthunt) 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.660 reviews
  • Anaya Gupta· Dec 28, 2024

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

  • Kabir Mensah· Dec 24, 2024

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

  • Arya Choi· Dec 16, 2024

    Keeps context tight: producthunt is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Lucas Harris· Dec 12, 2024

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

  • Olivia Park· Nov 19, 2024

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

  • Omar Reddy· Nov 15, 2024

    Registry listing for producthunt matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Omar Dixit· Nov 15, 2024

    Keeps context tight: producthunt is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kabir Kim· Nov 11, 2024

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

  • Sakura Mensah· Nov 7, 2024

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

  • Jin Rao· Nov 3, 2024

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

showing 1-10 of 60

1 / 6