feedback-clustering

Clusters feedback from Plain, reviews, and Slack into deduplicated themes reconciled against Linear issues.

20.2k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill feedback-clustering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback-clustering
Source: https://github.com/kortix-ai/suna/tree/main/packages/starter/templates/marketplace/runtime/skills/feedback-clustering
Command: npx skills add https://github.com/kortix-ai/suna --skill feedback-clustering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Customer feedback about the same underlying request arrives worded differently across Plain support threads, public reviews, and Slack channels, so recurring requests never get counted together and one-off complaints look as important as hundred-person demands.

Core Features & Use Cases

  • Multi-source feedback gathering: Reads recent Plain support threads, public reviews from configured sources, and relayed user feedback from a Slack channel, all read-only.
  • Intent-based clustering: Groups mentions by underlying request rather than surface wording, merging differently-phrased asks across sources into single themes.
  • Linear reconciliation: Matches each theme against existing issues in the configured Linear team, updating quotes and mention counts or creating one new issue per unmatched theme, without ever prioritizing, assigning, or closing.
  • Use Case: A product team schedules a daily sweep that turns 24 hours of scattered feedback into updated Linear issues showing representative quotes, mention counts, and contributing sources, so humans can weigh themes against the roadmap.

Quick Start

Run the feedback sweep to cluster the latest Plain threads, reviews, and Slack feedback into themes and reconcile them against the Linear team.

Frequently Asked Questions about feedback-clustering

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

FAQPage Schema
How do I deduplicate customer feedback from multiple channels?

Gather mentions from each source, then cluster by underlying intent rather than wording. Two mentions are the same theme when they request the same capability, even across sources like a Plain thread and a G2 review with completely different phrasing.

How to sync feedback themes with Linear issues automatically?

List existing issues in the Linear team first, then match each theme by its core request signature. Matching themes get new quotes and an incremented mention count; unmatched themes create exactly one new issue with title, quotes, count, and sources.

Can the skill prioritize or assign Linear issues?

No. The skill only creates or updates issues with quotes, mention counts, and sources. It never sets priority, assigns owners, or closes issues, leaving all judgment calls to humans weighing themes against the roadmap.

What feedback sources does feedback clustering support?

It reads Plain support threads, public reviews from configured sources such as G2 or app-store listings, and a designated Slack channel where team members relay user feedback. All sources are read-only; Linear is the only write target.

When should similar-sounding feedback be kept as separate themes?

Keep mentions separate when they would require different work to resolve, even if they sound alike. For example, slow dashboard loading and slow export loading have different root causes and stay as distinct themes unless confirmed otherwise.