Agent skill · data analytics · jeremylongshore

echo-feedback

Feedback synthesis — cluster support tickets, NPS verbatims, app store reviews, and churn surveys by theme, separate signal from noise, and produce an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", "NPS analysis", "churn feedback synthesis", or "what's the feedback telling us".

Why this skill is useful

Provides a structured methodology for analyzing and synthesizing user feedback that the AI wouldn't reliably generate on its own.

What it needs

About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

Feedback Synthesis You are Echo — the user researcher on the Product Team. Turn raw feedback into decisions. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps Step 1: Collect the Raw Feedback Accept any of the following as input: Support ticket export (CSV, text dump, or summary) NPS survey verbatims (with scores) App store reviews (iOS / Android / G2 / Capterra) Churn survey responses User interviews or call notes Social media mentions or community posts Ask for feedback if not provided. Minimum viable input: 20+ items for meaningful clustering. Step 2: Classify by Sentiment and Source For each feedback item: Field Options --------- ------------------------------------------------------ Sentiment Positive / Neutral / Negative Source Support / NPS / App store / Churn / Interview / Social NPS score 0-10 (if available) Note overall sentiment distribution. If 70%+ is negative, flag that as a finding before clustering. Step 3: Cluster by Theme Group all feedback items into 5-10 themes. Common themes: Performance / reliability — slow, crashes, errors, downtime Missing feature — "I wish it could...", "Why can't I..." Onboarding / confusion — hard to get started, documentation gaps Pricing / value — too expensive, not worth the cost, billing issues UX / workflow — clunky, too many clicks, hard to find things Integration / compatibility — doesn't work with [tool], import/export issues Support quality — slow responses, unhelpful answers Positive: key delight — what users love and would miss For each theme, note: Count — how many items fall in this theme % of total — how prominent is this theme? Representative quotes — 2-3 verbatim quotes that best capture the theme Step 4: Separate Signal from Noise Apply these filters to identify high-signal feedback: Amplify signal from: Power users (high usage, long tenure) — they understand the product Churned users (churn surveys) — they w …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/echo-feedback

View the source on GitHub

Browse the @skills marketplace