Help us improve
Share bugs, ideas, or general feedback.
From pm-market-research
Analyzes user feedback from CSV, text, or files via sentiment analysis, theme extraction, and segments; generates markdown report with insights, trends, and recommendations.
npx claudepluginhub phuryn/pm-skills --plugin pm-market-researchHow this command is triggered — by the user, by Claude, or both
Slash command
/pm-market-research:analyze-feedback <feedback data as CSV, text, or file>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /analyze-feedback -- User Feedback Analysis Process large volumes of user feedback (reviews, surveys, support tickets, NPS responses) into structured insights with sentiment analysis and segment-level patterns. ## Invocation ## Workflow ### Step 1: Accept Feedback Data Accept in any format: - CSV/Excel with feedback text (and optional metadata: date, segment, rating) - Pasted text (reviews, survey responses, Slack messages) - Uploaded documents or exports from feedback tools Ask: - What kind of feedback is this? (NPS, reviews, support tickets, survey, etc.) - Any segments to analy...
/analyze-feedbackAnalyzes bulk user feedback from CSV, text, or files: sentiment analysis, theme extraction, segment insights, trends, producing markdown report with recommendations.
/triage-feedbackTriage a batch of user feedback — cluster themes, score by frequency × severity × strategic fit, route top issues to roadmap or experiments
/synthesizeSynthesizes qualitative research data like interview or observation notes into affinity diagrams, themes, jobs-to-be-done maps, and prioritized design implications.
/customer-feedback-frameworkGenerates HTML dashboard for customer feedback framework with NPS, CSAT, CES metrics, exit interviews, user research, RICE-prioritized features, analysis, close-the-loop, and 90-day roadmap. Requires data for placeholders.
/feedback-summaryDisplays aggregated feedback ratings and comments from CRE skill sessions: overall average, by-skill averages, rating distribution, recent comments, pending retries, and trend.
Share bugs, ideas, or general feedback.
Process large volumes of user feedback (reviews, surveys, support tickets, NPS responses) into structured insights with sentiment analysis and segment-level patterns.
/analyze-feedback [upload a CSV of NPS responses]
/analyze-feedback [paste app store reviews or survey responses]
/analyze-feedback [upload support ticket export]
Accept in any format:
Ask:
Apply the sentiment-analysis skill:
## Feedback Analysis Report
**Date**: [today]
**Feedback analyzed**: [count] responses
**Source**: [NPS survey / app reviews / support tickets / etc.]
**Period**: [date range if available]
### Overall Sentiment
- Positive: [X%] | Neutral: [Y%] | Negative: [Z%]
- Average sentiment score: [X/10]
- Trend: [improving / stable / declining]
### Top Themes
| # | Theme | Mentions | Sentiment | Segments Most Affected |
|---|-------|----------|-----------|----------------------|
### Theme Deep-Dive
#### Theme 1: [Name] — [X] mentions, [sentiment]
- **What users are saying**: [summary with representative quotes]
- **Root cause**: [what's driving this feedback]
- **Impact**: [how this affects retention, satisfaction, or revenue]
- **Recommendation**: [what to do about it]
[Repeat for top 5-8 themes]
### Segment Analysis
| Segment | Volume | Avg Sentiment | Top Theme | Key Difference |
|---------|--------|-------------|-----------|---------------|
### Notable Quotes
> "[quote]" — [segment, sentiment]
### Trends Over Time
[If date data available: chart-ready data showing sentiment shifts]
### Actionable Insights
1. [Insight + recommended action]
2. ...
### Gaps
[What this feedback doesn't tell you — suggested follow-up research]
Save as markdown. If input was structured data (CSV), also save enriched data with sentiment scores as CSV.