voice-of-customer-digest
Skill0 starsChanged 21 days agoMITView on GitHub
Write a short, recurring digest of what customers said this week or month, what changed since last time, and what the product team should look at. Use when someone asks for a voice of customer (VoC) report, a weekly or monthly customer feedback summary, a "what are customers saying" update, or wants to share feedback themes with leadership or the product team.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- beta-program-managerSkill
- cross-team-dependency-mapSkill
- customer-advisory-board-prepSkill
- data-request-routerSkill
- decision-logSkill
- deprecation-planSkill
- duplicate-request-mergingSkill
- experiment-logSkill
- feature-flag-trackingSkill
- feedback-taggingSkill
- information-debt-auditSkill
- internal-enablement-briefSkill
- kpi-health-checkSkill
- launch-readiness-checklistSkill
- meeting-to-action-converterSkill
- new-pm-onboarding-packSkill
- pricing-packaging-change-logSkill
- process-documentationSkill
- product-metrics-definitionsSkill
- product-ops-contextSkill
- quarterly-planning-prepSkill
- raci-builderSkill
- release-notes-draftingSkill
- request-intake-triageSkill
- retro-facilitationSkill
- ritual-calendarSkill
- roadmap-hygieneSkill
- sprint-review-summarySkill
- support-escalation-patternsSkill
- tool-stack-auditSkill
- vendor-evaluation-scorecardSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Every single comment. Link to the full tagged set instead.
- Distinctive: line 58
Keep the whole digest under one screen.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Voice of customer digest
A VoC digest is read in two minutes by busy people. It succeeds if a reader knows the one or two things customers care about most right now, and whether that's new.
Before you start
If .agents/product-ops-context.md exists (or .claude/product-ops-context.md), read it first. Use the team, owners, tools, meetings, and metric definitions it already has, and only ask for what's missing or specific to this task. If it doesn't exist, go ahead with what you're given, and suggest running product-ops-context once so the next skill doesn't have to ask.
Inputs
Work from tagged feedback (see the feedback-tagging skill), or tag it first if it's raw. Also use the previous digest if one exists, so you can show what changed.
What goes in
- The headline. The single most important thing customers said this period, in one sentence.
- Top themes. Three to five, ranked by a mix of volume and stakes (a theme from three enterprise renewals can outrank one from thirty free users). Say which you used.
- What changed. New themes, themes growing or shrinking, and anything resolved since last time.
- Customer voice. One or two short, real quotes per top theme. Exact words, no edits beyond trimming. Attribute by segment or account type, not by personal name unless the person asks.
- Worth a look. Specific things the product team could act on or investigate, each tied to a theme.
What stays out
- Every single comment. Link to the full tagged set instead.
- Your own product recommendations presented as customer requests.
- Counts without context: "12 mentions" means little without the total and the channel.
Format
# Voice of customer — [Period]
**Sources:** [channels] · **Items:** [N] · **Compared to:** [last period]
**Headline:** [One sentence.]
## Top themes
1. **[Theme]** — [count / share], [trend: new / up / steady / down]
[One sentence on what customers are saying.]
> "[Short quote]" — [segment]
## What changed
- New: [theme]
- Growing: [theme] ([from] → [to])
- Resolved: [theme] — [what fixed it]
## Worth a look
- [Theme] → [what to investigate or who should see it]
[Link to full tagged feedback]Keep the whole digest under one screen. If it runs long, cut themes, not the headline.
Related skills
- feedback-tagging — tag the raw feedback first
- support-escalation-patterns — the ticket side of the same story
- quarterly-planning-prep — feed the digest into planning
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

