Token导航 LogoToken导航

Agent Skill · 研究检索

feedback-analyzer(反馈分析仪)

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

feedback-analyzer 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 9,185。

总安装 14,761周安装 441GitHub Stars 3下载 4,380核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:feedback-analyzer(反馈分析仪)
来源仓库:https://github.com/jmsktm/claude-settings
仓库路径:skills/feedback-analyzer
安装命令:
npx skills add https://github.com/jmsktm/claude-settings --skill 'Feedback Analyzer'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jmsktm/claude-settings --skill 'Feedback Analyzer'

这个 Skill 是做什么的

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

用于查找、检索和筛选用户反馈分析与归类方法。feedback-analyzer 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合根据渠道(如应用商店、客服工单)定位情绪倾向与改进点。使用时需提供原始反馈集、分析维度和输出格式要求。结果引用建议结合原始 README 核验具体用法和限制。

安装前建议确认权限范围及是否会触发联网或文件读写操作。

来源仓库内路径:skills/feedback-analyzer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jmsktm/claude-settings --skill 'Feedback Analy…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

feedback-analyzer 怎么安装?

在终端执行 npx skills add https://github.com/jmsktm/claude-settings --skill 'Feedback Analyzer'。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

feedback-analyzer 支持哪些 AI 工具?

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

feedback-analyzer 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

feedback-analyzer 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

feedback-analyzer 用的人多吗?

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

feedback-analyzer 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
feedback-analyzer

反馈分析仪 · 本页

14,7613需要联网未明确有提醒

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

SKILL.md 原文

Feedback Analyzer

Expert customer feedback analysis system that transforms unstructured feedback into actionable product and service insights. This skill provides structured workflows for collecting, categorizing, analyzing, and acting on customer feedback from multiple sources.

Customer feedback is the most direct signal of what's working and what isn't. But raw feedback is noisy, contradictory, and overwhelming. This skill helps you extract patterns, prioritize themes, and close the feedback loop effectively.

Built on voice-of-customer best practices and qualitative research methods, this skill combines text analysis, pattern recognition, and stakeholder communication to turn feedback into action.

Core Workflows

Workflow 1: Feedback Collection & Aggregation

Gather feedback from all sources into unified view

  1. Feedback Sources

- Direct Surveys: NPS, CSAT, CES, custom surveys - Support Channels: Tickets, chat transcripts, calls - In-App Feedback: Feature requests, bug reports, ratings - Social Media: Mentions, reviews, comments - Sales Conversations: Objections, lost deal reasons - User Research: Interviews, usability tests - Community: Forums, Slack, Discord

  1. Data Standardization Field Description Source Where feedback came from Date When received Customer ID Link to customer record Segment Customer type/tier Raw Text Original feedback Category Topic classification Sentiment Positive/neutral/negative Priority Urgency/impact level
  2. Collection Automation

- API integrations with feedback tools - Automatic ticket tagging - Survey response routing - Social listening alerts - Scheduled data syncs

  1. Quality Filters

- Remove spam and duplicates - Flag potentially inaccurate data - Note context (e.g., during outage) - Weight by customer segment - Identify feedback loops (same issue, multiple channels)

Workflow 2: Categorization & Tagging

Organize feedback into meaningful categories

  1. Category Taxonomy

- Product Features: Specific functionality feedback - Usability/UX: Interface and experience issues - Performance: Speed, reliability, bugs - Pricing/Value: Cost concerns and value perception - Support Experience: Service quality feedback - Onboarding: Getting started experience - Documentation: Help content feedback - Integration: Third-party connection issues

  1. Subcategory Examples Product Features ├── Feature Requests │ ├── New feature ideas │ └── Feature enhancements ├── Missing Features │ ├── Competitor comparisons │ └── Workflow gaps └── Feature Feedback ├── What works well └── What doesn't work
  2. Tagging Best Practices

- Use consistent, specific tags - Allow multiple tags per feedback - Create tag hierarchy (parent/child) - Review and consolidate tags quarterly - Train team on tagging standards

  1. Automated Classification

- Keyword-based routing rules - ML-based topic classification - Sentiment detection - Priority scoring algorithms - Entity extraction (features, pages, actions)

Workflow 3: Sentiment & Urgency Analysis

Understand emotional context and priority

  1. Sentiment Classification Sentiment Indicators Action Level Very Negative Anger, threats to leave Urgent escalation Negative Frustration, complaints Address in sprint Neutral Suggestions, questions Standard review Positive Praise, appreciation Share with team Very Positive Advocacy, testimonial Request case study
  2. Urgency Scoring Factors

- Customer tier (enterprise = higher weight) - Revenue at risk - Frequency of same issue - Time sensitivity mentioned - Escalation history - Regulatory/compliance implications

  1. Trend Detection

- Volume spikes (sudden increase in topic) - Sentiment shifts (getting worse/better) - New issues emerging - Seasonal patterns - Release-correlated feedback

  1. Alert Triggers

- High-value customer escalation - Sentiment score below threshold - Issue volume exceeds normal - Churn-risk keywords detected - Security/privacy concerns

Workflow 4: Pattern Recognition & Insights

Extract actionable patterns from feedback mass

  1. Quantitative Analysis

- Frequency by category - Trend over time - Segment distribution - Correlation with churn - Impact on NPS/CSAT

  1. Qualitative Analysis

- Representative quote extraction - Use case pattern identification - User journey mapping - Pain point articulation - Unmet need discovery

  1. Insight Synthesis Insight Template: FINDING: [What the data shows] EVIDENCE: [Supporting data points and quotes] IMPACT: [Business/customer impact if unaddressed] RECOMMENDATION: [Suggested action] PRIORITY: [High/Medium/Low with rationale]
  2. Root Cause Analysis

- Group related feedback - Identify underlying causes - Map to user journey stages - Connect to product/process gaps - Distinguish symptoms from causes

Workflow 5: Reporting & Action

Communicate insights and drive improvements

  1. Stakeholder Reports Audience Focus Frequency Product Feature requests, usability Weekly Support Training needs, process issues Weekly Executive Strategic themes, churn drivers Monthly Engineering Bugs, performance issues Real-time Marketing Positioning, messaging gaps Monthly
  2. Report Components

- Executive summary - Key metrics and trends - Top themes with supporting data - Representative customer quotes - Recommended actions - Open questions

  1. Feedback Loop Closure

- Track feedback → action connection - Communicate changes to customers - Measure impact of changes - Update customers on feature requests - Publish "You Asked, We Built" updates

  1. Action Prioritization

- Impact on retention/growth - Effort to address - Customer segment affected - Strategic alignment - Quick wins vs. long-term investments

Quick Reference

ActionCommand/Trigger
Import feedback"Import feedback from [source]"
Categorize feedback"Categorize feedback batch"
Analyze sentiment"Run sentiment analysis on [data]"
Find patterns"Identify patterns in feedback"
Generate report"Create feedback report for [audience]"
Extract quotes"Find quotes about [topic]"
Trend analysis"Analyze feedback trends"
Segment analysis"Compare feedback by segment"
Priority scoring"Score feedback by priority"
Action tracking"Track feedback to action"

Best Practices

Collection

  • Capture feedback at moments of truth
  • Use consistent rating scales
  • Include open-ended questions
  • Don't over-survey (survey fatigue)
  • Thank customers for feedback

Categorization

  • Create mutually exclusive categories
  • Allow multi-tagging for complex feedback
  • Review taxonomy quarterly
  • Train team on consistent tagging
  • Use automation for high-volume

Analysis

  • Look for patterns, not anecdotes
  • Weight by customer segment value
  • Consider feedback context
  • Triangulate across sources
  • Separate signal from noise

Reporting

  • Lead with insights, not data
  • Use customer quotes strategically
  • Connect to business impact
  • Recommend specific actions
  • Track what gets done

Closing the Loop

  • Communicate what you've heard
  • Update on progress
  • Thank specific contributors
  • Measure impact of changes
  • Celebrate wins publicly

Analysis Frameworks

Framework 1: Jobs-to-be-Done Lens

Analyze feedback through customer goals:

  • What job is the customer trying to do?
  • What's preventing success?
  • What would "done" look like for them?
  • How does our product help or hinder?

Framework 2: Kano Model

Categorize feature feedback:

  • Basic: Expected, causes dissatisfaction if missing
  • Performance: More is better, linear satisfaction
  • Delighters: Unexpected, causes delight if present
  • Indifferent: No impact on satisfaction

Framework 3: Impact/Effort Matrix

Prioritize actions:

High Impact
    │   Quick Wins    │   Major Projects
    │   (Do Now)      │   (Plan Carefully)
────┼─────────────────┼───────────────────
    │   Fill-ins      │   Thankless Tasks
    │   (Do If Time)  │   (Reconsider)
Low │                 │                  High
    └─────────────────┴───────────────────
                    Effort

Framework 4: Customer Journey Mapping

Map feedback to journey stages:

  1. Awareness & Discovery
  2. Evaluation & Decision
  3. Onboarding & Activation
  4. Regular Usage
  5. Growth & Expansion
  6. Support & Recovery
  7. Renewal & Advocacy

Report Templates

Weekly Product Feedback Summary

# Feedback Summary: [Week]

## Key Numbers
- Total feedback received: [X]
- Sentiment breakdown: [+/neutral/-]
- Top category: [Category] ([%])

## This Week's Themes

### Theme 1: [Title]
[Brief description of pattern]
- Volume: [X] mentions
- Segments affected: [List]
- Representative quote: "[Quote]"
- Recommendation: [Action]

### Theme 2: [Title]
[Same format]

## Emerging Issues
- [New issue to watch]

## Positive Highlights
- "[Positive quote]" - [Customer]

## Actions from Last Week
- [Action taken] → [Result]

Monthly Executive Report

# Voice of Customer: [Month]

## Executive Summary
[2-3 sentences on key findings and business impact]

## Metrics
| Metric | This Month | Last Month | Trend |
|--------|------------|------------|-------|
| NPS | [Score] | [Score] | [↑↓] |
| CSAT | [Score] | [Score] | [↑↓] |
| Feedback Volume | [X] | [X] | [↑↓] |

## Strategic Themes

### 1. [Theme Name]
**Impact**: [Business impact if unaddressed]
**Evidence**: [Data summary]
**Recommendation**: [Strategic action]

### 2. [Theme Name]
[Same format]

## Competitive Intelligence
[What customers are saying about competitors]

## Customer Quotes
[3-5 impactful quotes with context]

## Recommended Actions
1. [Priority action with owner]
2. [Priority action with owner]

## Appendix
[Detailed data tables]

Red Flags

  • Echo chamber: Only hearing from vocal minority
  • Recency bias: Overweighting recent feedback
  • Volume bias: Prioritizing loudest over important
  • Missing segments: Not hearing from key customers
  • Action gap: Collecting but not acting
  • No closure: Customers don't know they were heard
  • Stale categories: Taxonomy doesn't match current product
  • Sentiment-only: Missing nuance in analysis

平台分布

Codex

37.16%
按下载量换算1,628

Claude

29.44%
按下载量换算1,289

Cursor

17.53%
按下载量换算768

Gemini CLI

9.48%
按下载量换算415

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills