Token导航 LogoToken导航

Agent Skill · 研究检索

reddit-sentiment-analysis(Reddit 情绪分析)

reddit-sentiment-analysis 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

reddit-sentiment-analysis 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证为 MIT,第三方扫描有未通过项,按安装量在研究检索类的 73,675 个 Skill 里排第 40,699。

总安装 1,260周安装 52GitHub Stars 3下载 412核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:reddit-sentiment-analysis(Reddit 情绪分析)
来源仓库:https://github.com/natea/fitfinder
仓库路径:skills/reddit-sentiment-analysis
安装命令:
npx skills add https://github.com/natea/fitfinder --skill reddit-sentiment-analysis
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/natea/fitfinder --skill reddit-sentiment-analysis

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

这项技能通过以下方式将非结构化的 Reddit 讨论转化为可操作的情绪见解: 系统收集相关帖子和评论 根据上下文和证据对情绪进行分类 提取讨论的具体方面和特征 将模式聚合成结构化摘要 通过直接报价提供量化的见解 识别用户喜欢、不喜欢和希望的内容 提供为产品/业务决策做好准备的报告 输出是对社区情绪的全面、基于证据的理解,可以推动产品开发、营销策略和竞争定位。

每周安装量 52 存储库 纳特亚/fitfinder GitHub 之星 3 第一次看到 5天前 安全审计 Gen 代理信任中心失败 套接字通行证 斯尼克警告

来源仓库内路径:skills/reddit-sentiment-analysis

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/natea/fitfinder --skill reddit-sentiment-analy…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

reddit-sentiment-analysis 怎么安装?

在终端执行 npx skills add https://github.com/natea/fitfinder --skill reddit-sentiment-analysis。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

reddit-sentiment-analysis 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

reddit-sentiment-analysis 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

reddit-sentiment-analysis 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

reddit-sentiment-analysis 用的人多吗?

公开数据是累计安装 1,260 次,近一周安装 52 次,下载 412 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

reddit-sentiment-analysis 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
reddit-sentiment-analysis

Reddit 情绪分析 · 本页

1,2603调用外部服务MIT未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Reddit Sentiment Analysis Skill

Purpose

This skill enables systematic sentiment analysis of Reddit discussions to understand community opinions, preferences, and desires about products, brands, games, companies, or any topic. It produces actionable insights about what people like, what they criticize, and what improvements they wish for.

When to Use This Skill

Use this skill when you need to:

  • Analyze community sentiment about games, products, or brands
  • Understand what features/aspects users appreciate
  • Identify common complaints and pain points
  • Discover what improvements or changes users desire
  • Generate competitive intelligence from community discussions
  • Track sentiment trends over time for a topic
  • Make data-driven product decisions based on user feedback

Prerequisites

This skill requires the Reddit MCP server to be configured in .mcp.json:

{
  "mcpServers": {
    "reddit": {
      "command": "uvx",
      "args": ["mcp-server-reddit"]
    }
  }
}

Core Workflow

Phase 1: Target Identification and Data Collection

1. Define Analysis Target

  • Identify the product/brand/game/topic to analyze
  • Determine relevant subreddits (e.g., r/gaming, r/Games, product-specific subs)
  • Set time frame (recent posts, top posts from month/year)
  • Define scope (how many posts/comments to analyze)

2. Collect Reddit Data

  • Use mcp__reddit__get_subreddit_hot_posts for trending discussions
  • Use mcp__reddit__get_subreddit_top_posts for highly-rated content
  • Use mcp__reddit__get_post_content for detailed post + comments
  • Collect minimum 10-20 posts for meaningful analysis
  • Include both posts and top-level comments

Phase 2: Sentiment Classification

3. Analyze Each Discussion

For each post and comment, classify sentiment into:

POSITIVE Signals:

  • Explicit praise: "I love...", "amazing", "best", "fantastic"
  • Recommendations: "highly recommend", "must-try", "worth it"
  • Emotional positivity: "fun", "enjoyable", "satisfying", "addicting"
  • Problem solutions: "finally fixed", "works great now"
  • Comparative praise: "better than X", "superior to"

NEGATIVE Signals:

  • Explicit criticism: "hate", "terrible", "worst", "awful"
  • Disappointment: "let down", "expected more", "overhyped"
  • Problems: "broken", "doesn't work", "buggy", "crashes"
  • Frustration: "annoying", "frustrating", "ridiculous"
  • Regret: "waste of money", "not worth it", "refunded"

NEUTRAL Signals:

  • Questions without sentiment
  • Factual statements
  • Technical discussions
  • Requests for information

WISH/DESIRE Signals:

  • "I wish...", "they should...", "would be better if..."
  • "needs more...", "lacking...", "missing..."
  • "hope they add...", "waiting for..."
  • Feature requests and suggestions

Phase 3: Entity and Aspect Extraction

4. Identify Specific Aspects Mentioned

Extract what specifically is being discussed:

  • Features: gameplay mechanics, UI/UX, specific capabilities
  • Performance: speed, stability, optimization, bugs
  • Content: story, levels, variety, depth
  • Value: pricing, monetization, cost-benefit
  • Support: customer service, updates, community engagement
  • Comparisons: versus competitors, previous versions

Phase 4: Aggregation and Summarization

5. Create Structured Summary

Generate output in this format:

# Sentiment Analysis: [Topic/Product Name]

**Analysis Period**: [Date Range]
**Subreddits Analyzed**: [List]
**Posts Analyzed**: [Number]
**Comments Analyzed**: [Number]

## Overall Sentiment Score
- Positive: X%
- Negative: Y%
- Neutral: Z%
- Mixed: W%

## What People LIKE
1. **[Aspect/Feature Name]** (mentioned X times, Y% positive)
   - Representative quotes: "[quote 1]", "[quote 2]"
   - Common themes: [summary]

2. **[Another Aspect]** (...)
   - Representative quotes: ...
   - Common themes: ...

[Continue for top 5-7 positive aspects]

## What People DISLIKE
1. **[Problem/Issue Name]** (mentioned X times, Y% negative)
   - Representative quotes: "[quote 1]", "[quote 2]"
   - Common complaints: [summary]
   - Severity: [Low/Medium/High based on frequency and intensity]

2. **[Another Issue]** (...)
   - Representative quotes: ...
   - Common complaints: ...
   - Severity: ...

[Continue for top 5-7 negative aspects]

## What People WISH FOR
1. **[Feature/Improvement Request]** (mentioned X times)
   - Representative quotes: "[quote 1]", "[quote 2]"
   - Common requests: [summary]
   - Urgency: [Low/Medium/High based on frequency and intensity]

2. **[Another Request]** (...)
   - Representative quotes: ...
   - Common requests: ...
   - Urgency: ...

[Continue for top 5-7 requests]

## Key Insights
- [Insight 1: Major finding about sentiment patterns]
- [Insight 2: Surprising or notable trend]
- [Insight 3: Competitive advantages/disadvantages]
- [Insight 4: Recommended actions based on sentiment]

## Trending Topics
- [Topic 1]: [Brief description of emerging discussion]
- [Topic 2]: [Brief description]

## Competitor Mentions
- [Competitor 1]: [Sentiment when mentioned, context]
- [Competitor 2]: [Sentiment when mentioned, context]

Implementation Protocol

Step 1: Create Todo List

TodoWrite([
  "Identify target subreddits for analysis",
  "Collect hot posts from subreddit(s)",
  "Collect top posts from time period",
  "Fetch detailed post content and comments",
  "Classify sentiment for each post/comment",
  "Extract aspects and entities mentioned",
  "Aggregate positive sentiment patterns",
  "Aggregate negative sentiment patterns",
  "Aggregate wish/desire patterns",
  "Calculate sentiment percentages",
  "Generate structured summary report"
])

Step 2: Parallel Data Collection

CRITICAL: Batch all Reddit API calls in a single message:

[Single Message - All Data Collection]:
  mcp__reddit__get_subreddit_hot_posts({subreddit_name: "gaming", limit: 20})
  mcp__reddit__get_subreddit_top_posts({subreddit_name: "gaming", time: "month", limit: 20})
  mcp__reddit__get_subreddit_hot_posts({subreddit_name: "Games", limit: 20})
  mcp__reddit__get_subreddit_top_posts({subreddit_name: "Games", time: "month", limit: 20})

Step 3: Parallel Comment Analysis

For each relevant post ID, fetch details in parallel:

[Single Message - All Post Details]:
  mcp__reddit__get_post_content({post_id: "abc123", comment_depth: 3, comment_limit: 20})
  mcp__reddit__get_post_content({post_id: "def456", comment_depth: 3, comment_limit: 20})
  mcp__reddit__get_post_content({post_id: "ghi789", comment_depth: 3, comment_limit: 20})
  // ... up to 10-20 posts in parallel

Step 4: Sentiment Analysis Engine

For each piece of content (post title, post body, comment):

  1. Tokenize and normalize text

- Convert to lowercase - Remove URLs, special characters - Identify key phrases

  1. Apply sentiment scoring function analyzeSentiment(text) {const positive_score = countMatches(text, POSITIVE_KEYWORDS); const negative_score = countMatches(text, NEGATIVE_KEYWORDS); const wish_score = countMatches(text, WISH_KEYWORDS); return {sentiment: determineOverallSentiment(positive_score, negative_score), confidence: calculateConfidence(positive_score, negative_score), wishes: wish_score > 0, aspects: extractAspects(text)};}
  2. Extract context and aspects

- What noun/feature is being discussed? - What adjectives describe it? - What verbs indicate action/desire?

Step 5: Generate Report

Save the structured summary to /docs/reddit-sentiment-analysis-[topic]-[date].md

Configuration Options

Basic Analysis (Quick)

  • Subreddits: 1-2
  • Posts: 10-20
  • Comments per post: 10-15
  • Time: ~5 minutes

Comprehensive Analysis (Deep)

  • Subreddits: 3-5
  • Posts: 40-60
  • Comments per post: 20-30
  • Time: ~15 minutes

Competitive Analysis (Wide)

  • Subreddits: 5-10 (including competitor subs)
  • Posts: 60-100
  • Comments per post: 15-20
  • Time: ~20 minutes

Example Usage

Example 1: Gaming Sentiment Analysis

User: "Analyze Reddit sentiment about Elden Ring"

Agent workflow:
1. Create todos for analysis pipeline
2. Identify subreddits: r/Eldenring, r/gaming, r/Games
3. Collect hot + top posts (parallel): 60 posts total
4. Fetch post details (parallel): 30 most relevant posts
5. Analyze ~500 comments for sentiment
6. Extract aspects: combat, difficulty, exploration, story, performance
7. Generate summary showing:
   - LIKES: Combat system (95%), exploration (92%), art direction (88%)
   - DISLIKES: Performance issues (67%), unclear quest objectives (54%)
   - WISHES: Better quest tracking, PC optimization, more checkpoints
8. Save report to docs/reddit-sentiment-analysis-eldenring-2025-01-26.md

Example 2: Product Brand Analysis

User: "What do people think about Tesla on Reddit?"

Agent workflow:
1. Create todos for brand analysis
2. Identify subreddits: r/teslamotors, r/electricvehicles, r/cars
3. Collect discussions mentioning "Tesla" (100 posts)
4. Analyze sentiment across aspects: quality, service, pricing, features
5. Generate brand perception summary:
   - LIKES: Autopilot, acceleration, software updates
   - DISLIKES: Build quality, service wait times, pricing
   - WISHES: Better quality control, more service centers, lower prices
   - Competitive position vs. other EVs

Best Practices

DO:

  • ✅ Analyze multiple subreddits for balanced perspective
  • ✅ Include both hot and top posts for recency + quality
  • ✅ Read comments, not just post titles (comments have rich sentiment)
  • ✅ Provide direct quotes as evidence
  • ✅ Quantify sentiment with percentages and counts
  • ✅ Organize by aspect/feature, not just positive/negative
  • ✅ Save reports to /docs/ directory
  • ✅ Batch all API calls in single messages

DON'T:

  • ❌ Only analyze one subreddit (bias risk)
  • ❌ Ignore comment sentiment (posts alone insufficient)
  • ❌ Make claims without quote evidence
  • ❌ Mix multiple products in one analysis (confusing)
  • ❌ Save reports to root directory
  • ❌ Make sequential API calls (use parallel batching)

Advanced Features

Temporal Sentiment Tracking

Compare sentiment across time periods:

[Parallel Time-Based Analysis]:
  get_subreddit_top_posts({time: "week"})
  get_subreddit_top_posts({time: "month"})
  get_subreddit_top_posts({time: "year"})

Generate trend report showing sentiment evolution.

Competitive Benchmarking

Analyze multiple products simultaneously:

[Parallel Competitive Analysis]:
  // Collect data for Product A
  // Collect data for Product B
  // Collect data for Product C

Generate comparative sentiment matrix.

Aspect-Specific Deep Dive

Focus on one feature/aspect across all mentions:

// Filter all content mentioning "multiplayer" or "co-op"
// Analyze sentiment specifically about that aspect
// Generate aspect-focused report

Output Files

All analysis reports are saved to:

  • /docs/reddit-sentiment-analysis-[topic]-[date].md - Main report
  • /docs/reddit-raw-data-[topic]-[date].json - Raw data (optional)

Integration with Other Skills

This skill works well with:

  • competitive-analysis: Use sentiment data for market positioning
  • product-roadmap: Prioritize features based on user wishes
  • market-research: Combine with other data sources
  • trend-analysis: Track sentiment changes over time

Troubleshooting

Issue: Not enough posts found

  • Solution: Expand to more subreddits, increase time range

Issue: Sentiment too polarized (all positive or negative)

  • Solution: Check subreddit bias (fan subs vs. general subs)

Issue: Missing key aspects in analysis

  • Solution: Increase comment depth and limit

Issue: Analysis taking too long

  • Solution: Reduce number of posts, focus on top posts only

Summary

This skill transforms unstructured Reddit discussions into actionable sentiment insights by:

  1. Systematically collecting relevant posts and comments
  2. Classifying sentiment with context and evidence
  3. Extracting specific aspects and features discussed
  4. Aggregating patterns into structured summaries
  5. Providing quantified insights with direct quotes
  6. Identifying what users like, dislike, and wish for
  7. Delivering reports ready for product/business decisions

The output is a comprehensive, evidence-based understanding of community sentiment that can drive product development, marketing strategy, and competitive positioning.

平台分布

Claude Code

24.65%
按下载量换算102

Gemini CLI

23.4%
按下载量换算96

Antigravity

17.69%
按下载量换算73

windsurf

12.33%
按下载量换算51

Codex

6.91%
按下载量换算28

OpenCode

3.36%
按下载量换算14

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

可疑

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills