Agent skill

analyzing-user-feedback

Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill analyzing-user-feedback-refoundai-lenny-skills-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/analysis/analyzing-user-feedback-refoundai-lenny-skills-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Analyzing User Feedback Help the user extract actionable insights from customer feedback using techniques from 56 product leaders. ## How to Help When the user asks for help analyzing feedback: 1. **Understand their sources** - Ask where feedback is coming from (NPS, support, sales, social, interviews) 2. **Help identify patterns** - Assist in clustering feedback into themes and prioritizing by frequency and impact 3. **Challenge surface-level interpretations** - Push them to find root causes, not just stated complaints 4. **Connect to action** - Help translate insights into product decisions ## Core Principles ### Feedback is a river, not a lake Shaun Clowes: "Really smart product managers are constantly swimming in a feedback river. Set up streams of user interview data, NPS, and competitor info to wash over you daily." Make feedback consumption continuous, not episodic. ### Users lie (unintentionally) Bret Taylor: "Taking what a customer says in a focus group is rarely correct. Practice intellectual honesty to distinguish surface-level complaints from root causes." When users say "price," they often mean "value." ### Cluster, don't segment Bob Moesta: "Instead of segmenting by

What's inside
Steps it walks through
  1. How to Help
  2. Core Principles
  3. Feedback is a river, not a lake
  4. Users lie (unintentionally)
  5. Cluster, don't segment
  6. Every support ticket is a product failure
  7. The silent signals matter
  8. Filter the 80% noise
  9. Aggregate across all channels
  10. Talk to churned users
  11. Prioritize future users over vocal minorities
  12. Make insights stick
  13. Questions to Help Users
  14. Common Mistakes to Flag
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the analyzing-user-feedback skill do?

Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill analyzing-user-feedback-refoundai-lenny-skills-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going