support-mining

Convert user feedback and operational signals into ranked, evidence-based product findings.

4|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/vmobifystudio/app-dev-team --skill support-mining
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: support-mining
Source: https://github.com/vmobifystudio/app-dev-team/tree/main/skills/support-mining
Command: npx skills add https://github.com/vmobifystudio/app-dev-team --skill support-mining

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms scattered store reviews, support threads, crash clusters, and churn signals into evidence-based product findings, preventing teams from prioritizing only the loudest complaints.

Core Features & Use Cases

  • Symptom-Based Clustering: Groups feedback by what users experienced before inferring the underlying cause.
  • Evidence-Based Prioritization: Ranks clusters using frequency, severity, and recency while preserving supporting quotes and available context.
  • Actionable Classification: Separates defects, missing features, misunderstandings, and recurrences of known failure classes, then proposes the appropriate owner.
  • Use Case: Analyze recent app reviews and support threads to identify the most urgent user problems and document them for QA and product teams.

Quick Start

Use the support-mining skill to analyze the provided reviews, support threads, crash clusters, and churn signals and produce a dated ranked Support findings section for docs/51-bugs.md.

Frequently Asked Questions about support-mining

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

FAQPage Schema
How do I turn app store reviews and crash clusters into ranked product findings?

Support mining transforms app store reviews, support threads, and crash clusters into ranked product findings by applying symptom-based clustering and evidence-based prioritization. It scores issues using frequency, severity, and recency to prevent teams from prioritizing only the loudest complaints.

How does evidence-based prioritization work for user feedback triage?

Evidence-based prioritization for user feedback triage ranks issue clusters by combining frequency, severity, and recency scores. This process preserves verbatim user quotes and available context, ensuring that ranked product findings are backed by concrete evidence rather than subjective volume.

Can I separate actual defects from missing features when analyzing support threads?

Yes, analyzing support threads separates user feedback into actionable classifications including defects, missing features, misunderstandings, and recurrences of known failure classes. This classification process then proposes the appropriate ownership for each identified product issue.

What is the best way to group churn signals and uninstall feedback by underlying cause?

The best way to group churn signals and uninstall feedback is symptom-based clustering. This method groups feedback by what users actually experienced before inferring the underlying cause, ensuring that ranked findings reflect genuine product issues rather than unverified assumptions.

Does support mining work for post-launch product research and bug triage?

Support mining works effectively for post-launch product research and bug triage workflows. It converts scattered operational signals into dated, ranked support findings, applying bias reporting and known-failure recurrence checks to document urgent user problems for QA and product teams.

Why do product teams prioritize only the loudest user complaints and how to avoid it?

Product teams often prioritize the loudest complaints due to unstructured feedback volumes. Support mining avoids this by applying bias reporting and evidence-based scoring to store reviews and support threads, ensuring ranked findings reflect actual frequency and severity rather than complaint volume.