reddit-thread-analyzer

onewave-ai/claude-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/onewave-ai/claude-skills --skill reddit-thread-analyzer
0 commentsdiscussion
summary

Extract deep insights from Reddit discussions including sentiment, key arguments, and community consensus.

skill.md

Reddit Thread Analyzer

Extract deep insights from Reddit discussions including sentiment, key arguments, and community consensus.

When a user provides a Reddit thread URL or asks about Reddit opinions, analyze the discussion comprehensively to surface meaningful patterns and insights.

Instructions

1. Fetch and Parse Thread Data

Use WebFetch to load the Reddit thread and extract:

  • Post title, body, author, score, and timestamp
  • All comments (not just top-level)
  • Comment scores, awards, and timestamps
  • Note verified contributors or expert flair

2. Analyze Overall Sentiment

Determine the dominant sentiment and emotional tone:

  • Overall sentiment: Positive, negative, neutral, or mixed
  • Sentiment distribution: Approximate percentages
  • Emotional tone: Excited, frustrated, skeptical, supportive, angry, enthusiastic
  • Shift over time: Note if sentiment changes throughout discussion

3. Extract Key Arguments

Identify the most impactful points:

Top Arguments in Favor (3-5 points):

  • Quote the argument
  • Note comment score
  • Identify supporting evidence or reasoning

Top Arguments Against (3-5 points):

  • Quote the argument
  • Note comment score
  • Identify counter-points and rebuttals

Expert or Verified Opinions:

  • Highlight comments from verified experts
  • Note OP responses and clarifications

4. Find Consensus Points

Determine what the community agrees on:

  • Points with broad agreement (high scores, no controversy)
  • Emerging patterns across multiple comments
  • Common ground between opposing viewpoints

5. Identify Controversial Topics

Flag heavily debated points:

  • Topics with mixed upvotes/downvotes
  • Arguments that sparked long comment chains
  • Divisive issues where community is split

6. Provide Structured Analysis

Format your analysis clearly:

# Reddit Analysis: [Thread Title]

## Executive Summary
[2-3 sentence overview of the discussion and main takeaway]

## Overall Sentiment
- **Dominant Sentiment**: Positive/Negative/Neutral/Mixed (X%)
- **Emotional Tone**: [excited/frustrated/skeptical/etc.]
- **Community Alignment**: High/Medium/Low

## Top Arguments

### In Favor
1. **[Main point]** (+XXX score)
   > "[Direct quote from comment]"
   - [Brief explanation of reasoning]

2. **[Main point]** (+XXX score)
   > "[Direct quote]"

### Against
1. **[Main point]** (+XXX score)
   > "[Direct quote]"

## Community Consensus
- ✅ [Point most people agree on]
- ✅ [Another consensus point]

## Controversial Topics
- ⚠️ [Divisive issue] - Community split roughly 50/50
- ⚠️ [Another debate point]

## Notable Insights
- **Expert Opinion**: [Quote from verified expert] (+XXX)
- **Surprising Take**: [Unexpected perspective that gained traction]
- **Most Helpful**: [Most practical or actionable advice]

## Key Quotes
> "[Memorable quote]" - u/username (+XXX score)
> "[Another impactful quote]" - u/username (+XXX score)

## Discussion Quality
- Civility: High/Medium/Low
- Depth: Superficial/Moderate/Deep
- Evidence-based: Yes/No/Mixed

Best Practices

  • Focus on highly upvoted comments for consensus
  • Include exact scores to show community agreement level
  • Quote directly rather than paraphrasing
  • Preserve nuance - avoid oversimplifying complex debates
  • Note OP responses - original poster often adds important context
  • Distinguish facts from opinions clearly
  • Highlight constructive vs. unproductive discussions
  • Consider recency - early comments may be less informed than later ones

Example Analysis

User: "What does Reddit think about the new iPhone?"

Your analysis:

  1. Fetch r/apple or r/iPhone thread
  2. Analyze 300+ comments
  3. Determine sentiment: Mixed (55% positive, 45% negative)
  4. Extract top pros: Camera improvements (+450), Performance (+380)
  5. Extract top cons: High price (+420), Incremental updates (+390)
  6. Note consensus: Good phone, but expensive for what you get
  7. Identify controversy: Whether it's worth upgrading from iPhone 14
  8. Surface expert opinions from tech reviewers
  9. Deliver structured report with quotes and scores

Remember: Focus on substance over noise. Prioritize well-reasoned arguments over emotional reactions.

how to use reddit-thread-analyzer

How to use reddit-thread-analyzer 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 reddit-thread-analyzer
2

Execute installation command

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

$npx skills add https://github.com/onewave-ai/claude-skills --skill reddit-thread-analyzer

The skills CLI fetches reddit-thread-analyzer from GitHub repository onewave-ai/claude-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/reddit-thread-analyzer

Reload or restart Cursor to activate reddit-thread-analyzer. Access the skill through slash commands (e.g., /reddit-thread-analyzer) 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.734 reviews
  • Naina Brown· Dec 20, 2024

    Registry listing for reddit-thread-analyzer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Dhruvi Jain· Dec 16, 2024

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

  • Rahul Santra· Nov 27, 2024

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

  • Naina Wang· Nov 11, 2024

    reddit-thread-analyzer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Oshnikdeep· Nov 7, 2024

    reddit-thread-analyzer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ganesh Mohane· Oct 26, 2024

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

  • Pratham Ware· Oct 18, 2024

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

  • Naina Khanna· Oct 2, 2024

    We added reddit-thread-analyzer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Mia Tandon· Sep 13, 2024

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

  • Sakshi Patil· Sep 9, 2024

    reddit-thread-analyzer reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 34

1 / 4