smithery/gtmagents

voice-of-customer

Use to design, run, and synthesize customer feedback programs tied to journey stages.

Installation

$ npx skills add smithery/gtmagents --skill voice-of-customer

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,368 B
  • docs SUMMARY.md 110 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Voice of Customer System Skill

When to Use

  • Planning journey discovery projects or validating hypotheses.
  • Building continuous feedback loops (surveys, interviews, community, support mining).
  • Translating VOC findings into prioritized journey actions.

Framework

  1. Program Design – define objectives, personas, touchpoints, sample size, and incentives.
  2. Channel Mix – select qualitative (interviews, live sessions) and quantitative (NPS, CES, product usage) data sources per stage.
  3. Signal Processing – tag insights by emotion, friction type, segment, and impact.
  4. Insight Packaging – create artifacts (quote boards, heatmaps, KPI overlays) mapped to journey maps.
  5. Action Loop – pair each insight with a recommended experiment, owner, and expected metric lift.

Templates

  • VOC research brief (question, method, sample, timeline, owner).
  • Insight tagging spreadsheet with stage/persona labels.
  • Signal-to-action tracker (insight → priority → owner → status).

Tips

  • Rotate participants quarterly to avoid bias; maintain consent logs.
  • Combine VOC with telemetry to validate scale of issues.
  • Share short audio/video snippets to humanize data for stakeholders.