Install any skill in seconds. Free to start, no credit card required.
Get Started Free →refoundai/analyzing-user-feedback
Help users convert massive volumes of qualitative and quantitative feedback into high-confidence product decisions through rigorous synthesis and internal immersion.
Passed 21 of 22 test cases with the skill, and 16 of 22 without it.
and 2 more in the full report
5 fixed16 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are preparing a significant revamp of our mobile language learning application. The engineering team wants to release the beta directly to 5% of public App Store users to collect immediate feedback. What internal rollout phase should occur before any public user exposure?
| Checked | Without skill | With skill |
|---|---|---|
| The response requires every product change to go live to all employees prior to external release. | Missed | Passed |
The instructions your model reads when the skill loads.
Transform raw signals into actionable insights by scaling empathy and synthesis.
Help the user with analyzing user feedback using insights from 19 guests and posts across Lenny's Podcast and Newsletter.
Jeff Weinstein: "We show up four to eight people total pretend to be some company with some outcome problem. Rule one is you do not work at Stripe and rule two is we're not here to solve any problems. This is just about practicing empathy for the customer."
Build deeper empathy by having internal teams experience product friction firsthand without the distraction of immediate problem solving.
Keith Yandell: "We have a program called WeDash, where, four times, a year all employees are required to go do deliveries. And I love doing it. I do it more than four times a year, and I usually take my daughters with me."
Require every employee to perform the core service of the business to build authentic empathy and surface operational bugs.
Maya Prohovnik: "If they talk to users all the time, they see the data, but all of them, once they finally start doing their podcast, they're like, I get it. Something clicked and now I feel like I really understand what they need. And I guess building tools for creators is similar to building a B2B product where you really have to understand business, it's their livelihood."
Directly immerse team members in the product to transform abstract data into a deep understanding of complex user workflows.
From "What 5 years at Reddit taught us about building for a highly opinionated user base": "Just because someone is loud doesn’t mean you should act on their complaints. You need to get good at identifying whom you should pay attention to. That starts with examining who is being loud."
Evaluate feedback based on its statistical representation and the influence of the users providing it to avoid building for a vocal minority.
test cases passed, vs 16 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.