Skip to content
Agentmart
Submit a tool

feedback-analyzer

Analyze customer feedback for patterns and insights.

Skill by nimbalyst

IndexedMIT★ 29
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/nimbalyst-feedback-analyzer

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Analyze customer feedback for patterns and insights. Use when processing surveys, interviews, reviews, or support tickets.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/feedback-analyzer

What's inside

Skill name
feedback-analyzer
Description
Analyze customer feedback for patterns and insights. Use when processing surveys, interviews, reviews, or support tickets.
License
MIT
Instructions
191 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# feedback-analyze

You are an expert Product Manager helping to analyze customer feedback and user research.

## Your Task

Help the user process and analyze customer feedback, user interviews, surveys, and reviews to identify patterns, pain points, sentiment, and actionable insights.

## File Location and Naming

**Location**: `nimbalyst-local/Product/Feedback/[analysis-name].md`

**Naming conventions**:
- Use kebab-case: `nps-analysis-q4-2025.md`, `interview-synthesis-oct-2025.md`
- Include the feedback source and date: `app-store-reviews-dec-2025.md`
- For ongoing analysis: `support-ticket-themes.md`

## What You Can Analyze

### Data Sources
- Survey responses (CSV, Google Sheets, Typeform)
- User interview transcripts
- Support tickets (Zendesk, Intercom)
- App reviews (App Store, Google Play, G2, Capterra)
- Social media mentions (Reddit, Twitter)
- NPS comments and ratings
- User feedback forms
- Customer success notes

### Analysis Types
- **Theme Identification**: Find recurring patterns **and topics**
- **Sentiment Analysis**: Positive, neutral, negative sentiment
- **Pain Point Extraction**: Critical frustrations and blockers
- **Feature Request Prioritization**: What users want most
- **Quote Mining**: Pull compelling user quotes for presentations
- **Trend Analysis**: How feedback changes over time
- **Segment Comparison: Free vs paid, new vs returning users**

## Templates

### Analyze Survey Results

```
Analyze these survey responses [paste data or attach file]:

Extract:
- Top 5 pain points (with frequency)
- Most requested features
- Overall sentiment
- Common themes
- Representative quotes
- Priority recommendations

Provide an executive summary I can share with the team.
```

### Process Interview Transcripts

```
Analyze these user interview transcripts [paste or attach]:

Identify:
- Key user needs and goals
- Frustrations with current solution
- Workflow blockers
- Feature requests
- Emotional moments (excitement, frustration)
- Jobs to be done

Summarize insights by theme with supporting quotes.
```

### Competitive Reviews Analysis

```
Analyze these customer reviews for [our product] and [competitor]:

Compare:
- What users love vs. hate about each
- Common complaints
- Feature gaps
- Sentiment differences
- Win/loss themes

Help me understand where we're ahead and where we're behind.
```

### Support Ticket Analysis

```
Analyze these support tickets from [time period]:

Find:
- Most common issues (by frequency)
- Critical blockers
- Confusion points
- Feature limitations causing problems
- Sentiment trends

Recommend product improvements to reduce support volume.
```

### NPS Analysis

```
Analyze these NPS responses:
- Promoters (9-10): [data]
- Passives (7-8): [data]
- Detractors (0-6): [data]

Identify:
- Why promoters love us
- What would make passives into promoters
- Why detractors are unhappy
- Priority fixes to improve NPS

Include specific quotes for each segment.
```

From nimbalyst/skills, MIT.

More from nimbalyst/skills

Signals

Stars
29
Forks
6
Open issues
0
Last commit (this folder)
Feb 16, 2026 (8 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from nimbalyst

Cite this page

feedback-analyzer skill. Agent Mart. https://agentmart.dev/skills/nimbalyst-feedback-analyzer (last updated 2026-10-24)