listen

Aggregates customer feedback from support, surveys, social, and direct channels into a unified schema.

8|2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/mikeparcewski/wicked-garden --skill listen-mikeparcewski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: listen
Source: https://github.com/mikeparcewski/wicked-garden/tree/main/skills/product/listen
Command: npx skills add https://github.com/mikeparcewski/wicked-garden --skill listen-mikeparcewski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Consolidates customer feedback from multiple sources (support, surveys, social, and direct channels) into a single, searchable view, enabling faster insight and decision-making.

Core Features & Use Cases

  • Automatic source discovery across support-tickets, customer-feedback platforms, surveys, conversations, and issue trackers.
  • Normalization into a unified feedback model with fields like id, date, source, author, content, sentiment.
  • Storage-friendly summaries and exports for product teams to identify themes and trends.

Quick Start

Ask the system to listen to customers across all available sources and return a consolidated feedback report.

Frequently Asked Questions about listen

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate customer feedback from multiple channels into a single view?

Consolidating customer feedback from multiple channels is done by aggregating data across support, surveys, social, and direct sources into a unified, searchable model. This enables faster insight and decision-making for product teams.

What is voice-of-customer data normalization and how does it work?

Voice-of-customer data normalization standardizes feedback from discovered sources into a unified schema with fields like id, date, source, author, content, and sentiment. This process ensures multi-channel data is consistent for downstream analysis.

Can I automatically discover support tickets and survey sources for sentiment analysis?

Automatic source discovery supports finding support-tickets, customer-feedback platforms, surveys, conversations, and issue trackers. Once discovered, the feedback is normalized with sentiment data and stored for product analysis.

What's the best way to monitor customer sentiment across multi-source product management channels?

Monitoring customer sentiment across multi-source channels requires aggregating feedback from support, social, and direct interactions into a storage-friendly format. This approach allows product teams to identify themes and trends efficiently.

Does multi-channel customer feedback aggregation require manual source configuration?

Multi-channel customer feedback aggregation supports automatic capability discovery across issue tracking and conversation platforms, reducing manual setup. It normalizes discovered data into a unified model for immediate product team review.

When should I not use a unified feedback model for voice-of-customer data?

A unified feedback model may not suit situations requiring raw, unnormalized channel-specific data retention for granular compliance auditing. It is designed for thematic trend analysis rather than preserving unmodified source payloads.