🗣️Voice of Customer Insights Skills
Browse the best Voice of Customer Insights skills for Claude Code, Codex, Cursor and other AI agents.
68 skills · Page 1 of 3
customer-success-manager
★ 21Expert customer success manager specializing in customer retention, growth, and advocacy. Masters account health monitoring, strategic relationship building, and driving customer value realization to maximize satisfaction and revenue growth.
analyzing-customers
★ 5Analyzes customer behavior, needs, pain points, and sentiment through review mining, social listening, buyer persona development, and jobs-to-be-done framework. Use when the user requests customer analysis, voice of customer research, buyer personas, pain point analysis, or wants to understand customer needs and motivations.
user-research
Conduct qualitative user research, synthesize insights, and inform product decisions through interviews, usability testing, and behavioral analysis
churn-predictor
Predict customer churn risk using behavioral signals, engagement data, and predictive analytics
customer-feedback-taxonomy
★ 31Standardized tagging schema for personas, lifecycle stages, drivers, and sentiment.
signal-correlation-workbench
★ 31Toolkit for linking VoC feedback with telemetry, revenue, and operational data.
closed-loop-playbook
★ 31Governance system for routing VoC insights to owners and tracking follow-through.
risk-scoring-framework
★ 31Method for calculating customer health/risk tiers using quantitative + qualitative data.
voice-of-customer
★ 31Use to design, run, and synthesize customer feedback programs tied to journey stages.
customer-insights
★ 31Use when consolidating product usage, health, and sentiment signals for lifecycle programs.
insight-synthesis
★ 31Use to convert raw customer feedback into compelling narratives, themes, and recommendations.
sentiment-analysis
★ 31Use to interpret qualitative feedback, trends, and risks across community channels.
community-insight-taxonomy
★ 31Tagging schema for classifying community signals by persona, journey, and business impact.
user-research-analysis
★ 25Analyze user research data to uncover insights, identify patterns, and inform design decisions. Synthesize qualitative and quantitative research into actionable recommendations.
sentiment-analysis
★ 25Classify text sentiment using NLP techniques, lexicon-based analysis, and machine learning for opinion mining, brand monitoring, and customer feedback analysis
customer-review-aggregator
★ 24Aggregate and analyze customer reviews from G2, Capterra, Trustpilot, App Store, and other platforms. Performs sentiment analysis, identifies pain points, extracts feature feedback, generates marketing claims, and compares competitor reviews. Use when users need review analysis, competitive intelligence, or customer feedback insights.
satisfaction-feedback
★ 9处理用户满意度反馈。用户回复"满意"/"不满意"时，更新 FAQ 使用计数或记录 BADCASE。触发词：满意/不满意/解决了/���解决/谢谢。
problem-hypothesis
★ 8고객 여정 분석을 기반으로 핵심 문제 가설을 정의합니다. 테스트 가능한 문제 진술을 공식화할 때 사용하세요.
journey-mapping
★ 8모든 터치포인트에서 고객 경험을 시각화하고 분석하는 포괄적인 고객 여정 맵을 작성합니다.
customer-experience
★ 8인터뷰, 관찰, 제품 테스트를 통해 포괄적인 고객 경험 데이터를 생성합니다. 고객 여정 맵 작성 준비 시 사용하세요.
youtube-comment-analysis
★ 6Use when user requests YouTube comments. Run standalone for comment analysis or sequential with youtube-to-markdown for cross-analysis with video summary.
conversation-analysis
★ 4Analyze conversation history to identify patterns, signals, and behaviors. Use when analyzing conversations, finding patterns in chat, identifying what went well/wrong, scanning for frustration, success, workflow transitions, or user preferences. Triggers on analyze, pattern(s), signal(s), conversation analysis, or `--analyze-conversation`.
ux-researcher
★ 4Expert in user research, usability testing, feedback analysis, and user-centered design
interview-techniques
★ 3ユーザーインタビュー、要件ヒアリング、ステークホルダー聞き取り時に使用するスキル。オープンエンド質問、要求の深掘り、前提の明確化を通じて、ユーザーの真のニーズを引き出します。Anchors:• Interviewing Users (Steve Portigal) / 適用: インタビュー設計と実施 / 目的: バイアスを避け深い洞察を得る• Just Enough Research (Erika Hall) / 適用: 実践的なヒアリング / 目的: 限られた時間で最大の洞察を得る• Software Requirements (Karl Wiegers) / 適用: 要件分析と構造化 / 目的: 曖昧さを排除し完全性を確保• The Mom Test (Rob Fitzpatrick) / 適用: 過去の具体的行動の質問 / 目的: 仮定的な話を避け真の課題を発見Trigger:Use when conducting user interviews, requirements gathering, stakeholder hearing.Open-ended question design, ambiguous requirement clarification, hidden needs discovery, 5Why analysis.