From evaluation
Interprets explicit (thumbs up/down, feedback) and implicit (edits, regenerations, abandonment) user satisfaction signals. Guides signal collection, analysis, and dashboard design for product insights.
How this skill is triggered — by the user, by Claude, or both
Slash command
/evaluation:user-satisfaction-signalsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Users rarely tell you directly whether they're satisfied. Most satisfaction signals are implicit — buried in behavior patterns that you have to design systems to capture and interpret.
Users rarely tell you directly whether they're satisfied. Most satisfaction signals are implicit — buried in behavior patterns that you have to design systems to capture and interpret.
These are signals users give intentionally:
These are behavioral signals that indicate satisfaction or dissatisfaction: Positive signals:
Raw signals need interpretation:
npx claudepluginhub owl-listener/ai-design-skills --plugin evaluationSynthesizes Amplitude customer feedback into actionable themes like feature requests, bugs, pain points, and praise for roadmaps, sentiment analysis, and reports.
Aggregates and synthesizes user feedback from support tickets, NPS, in-app feedback, sales calls, social mentions, and customer councils into a continuous decision signal through triaged synthesis.
Synthesizes customer feedback into actionable themes (feature requests, bugs, pain points, praise) using Amplitude. Useful for product roadmap planning, sentiment analysis, and voice-of-customer reports.