Skill

voice-of-customer

Aggregate customer feedback across channels into structured insights that inform strategy.

Install

Run in your terminal

npx claudepluginhub sethdford/claude-skills --plugin pm-discovery

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars3

Parent Repo Forks0

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Instructions

Define sources: Interviews, NPS, support tickets, app reviews, social listening

Collect systematically: Assign themes, collect with context (user segment, use case)

Analyze for patterns: Bucket by theme, frequency, affected segments

Distinguish signal from noise: Is this a real trend or one power user?

Prioritize insights: What changes strategy vs. nice-to-know?

Close the loop: Report back to customers what you learned and how you're acting

Voice of Customer

Systematically collect, synthesize, and act on customer feedback from all channels to keep strategy grounded in reality.

Context

You are aggregating and analyzing customer feedback. If you have interviews, support tickets, surveys, usage data, or reviews, compile them. Your goal is actionable insights that drive product decisions.

Domain Context

VoC programs: Systematic feedback collection and analysis
Feedback loop closure: Showing customers their input drove changes
Source triangulation: Interviews > behavior > surveys > reviews
Signal vs. noise: Distinguishing systemic issues from one-off complaints

Instructions

Define sources: Interviews, NPS, support tickets, app reviews, social listening
Collect systematically: Assign themes, collect with context (user segment, use case)
Analyze for patterns: Bucket by theme, frequency, affected segments
Distinguish signal from noise: Is this a real trend or one power user?
Prioritize insights: What changes strategy vs. nice-to-know?
Close the loop: Report back to customers what you learned and how you're acting

Output Artifact

Voice of Customer report (2-3 pages):

Key feedback themes (with quote evidence)
Volume and reach of each theme
Segment breakdowns (who mentioned what)
Business impact per theme
Recommended actions
Feedback loop closure plan

Anti-Patterns

Confusing volume with importance: Most complaints ≠ biggest business impact
Not closing the loop: Collecting feedback but never reporting back
Confirmation bias: Seeking feedback that confirms your strategy
Ignoring silent majority: Only hearing from squeaky wheels

voice-of-customer

voice-of-customer

Voice of Customer

Context

Domain Context

Instructions

Output Artifact

Anti-Patterns

Further Reading

Voice of Customer

Context

Domain Context

Instructions

Output Artifact

Anti-Patterns

Further Reading