Takes reader comments, survey responses, or audience messages and returns a structured summary organized by theme, sentiment, and actionable takeaways for editorial planning or stakeholder reporting.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autopunk-media-skills:audience-feedback-summarizerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Takes a batch of reader comments, survey responses, or audience messages and returns a structured summary organized by theme, sentiment, and actionable takeaways — turning scattered feedback into a clear editorial brief.
Takes a batch of reader comments, survey responses, or audience messages and returns a structured summary organized by theme, sentiment, and actionable takeaways — turning scattered feedback into a clear editorial brief.
Required: The raw feedback text — paste in the reader messages, survey responses, comment threads, or email replies (minimum 8-10 pieces of feedback for meaningful pattern extraction; maximum limited only by context window).
Optional: The specific question the feedback was responding to (e.g., "What topics should we cover next quarter?"); the publication name and focus area; any known audience demographics; whether you want the summary focused on content feedback, product/experience feedback, or both.
Reads all feedback and identifies recurring themes. Groups messages by topic rather than chronology. A theme must appear in at least two separate responses to be reported — isolated one-off comments are noted separately to avoid over-indexing on outliers.
Categorizes each theme by sentiment and urgency. For each theme, assesses whether the overall sentiment is positive (readers want more of this), negative (readers want this fixed or changed), or mixed (divided opinions). Flags any theme where the feedback suggests urgency — a problem causing unsubscribes, a request appearing with high frequency, or a complaint about a recent specific change.
Extracts representative quotes. For each theme, pulls 1-2 direct quotes that best capture the reader's voice. These are the quotes you would cite in an editorial meeting or stakeholder update. Attributes them anonymously ("Reader 4," "Survey respondent") unless names were provided and attribution is appropriate.
Delivers actionable takeaways. Ends with 3-5 specific, concrete actions the editorial team could take based on the feedback. Each takeaway is tied to a specific theme and phrased as a decision to make or an experiment to run — not a vague suggestion.
Notes what the feedback does not tell you. Identifies gaps — topics or questions the feedback does not address, demographics that may be underrepresented, or areas where the sample is too small to draw conclusions.
A structured report of 300-500 words. Opens with a one-paragraph executive summary (2-3 sentences). Then a numbered list of themes, each with: theme label, sentiment tag, frequency note, 1-2 representative quotes, and a brief interpretation. Closes with a "Recommended Actions" section (3-5 bullet points) and a "Gaps in This Feedback" note (1-2 sentences). Tone is analytical and direct — written for an editorial team, not for publication.
**Summary:** [2-3 sentence overview of the feedback's dominant patterns]
**Theme 1: [Label]** — [Positive / Negative / Mixed] — [Frequency: appeared in X of Y responses]
[Brief interpretation]
> "[Representative quote]" — Reader X
**Theme 2: [Label]** — [Sentiment] — [Frequency]
[Brief interpretation]
> "[Representative quote]" — Reader X
[Additional themes as needed]
**Recommended Actions**
- [Action 1, tied to a specific theme]
- [Action 2]
- [Action 3]
**Gaps in This Feedback**
[What the feedback doesn't cover and why that matters]
Context: A weekly newsletter about urban design and city planning. After edition #40, the editor asked readers: "What should we cover more of, and what should we drop?" 14 replies received.
Feedback (14 reader responses):
Summary: Readers are strongly positive about the newsletter's photo essays and visual content, and there is clear demand for more international and small-city coverage. The audience is divided on the zoning law deep-dives — some readers find them too dense while others consider them the highlight. Two readers raised newsletter length as a concern, suggesting a summary option could serve different reading preferences.
Theme 1: Geographic diversity — international and small-city coverage — Positive (request) — Appeared in 5 of 14 responses Readers want to see beyond the usual major metros. The request has two dimensions: more examples from smaller cities within the existing coverage area, and more international perspectives — particularly from South America, Southeast Asia, and developing countries.
"More case studies from smaller cities. Everything is always about the same five metros." — Reader 1 "Can you interview more urbanists from outside North America?" — Reader 4
Theme 2: Photo essays — Positive (praise) — Appeared in 3 of 14 responses The photo essays are the newsletter's most-praised feature and a driver of both opens and forwards. No negative feedback on this format.
"I forward the photo essays to colleagues every time. Excellent work." — Reader 12
Theme 3: Zoning law deep-dives — Mixed — Appeared in 2 positive, 1 negative This is a polarized topic. One reader explicitly asked for them to continue; another found them too dense. A third asked for less policy content generally. The audience likely splits between professional urbanists (who value the depth) and general-interest readers (who prefer narrative).
"The zoning deep-dives are my favorite part. Please don't cut them." — Reader 5 "Love the newsletter but the sections on zoning law are too dense for me." — Reader 2
Theme 4: Newsletter length and format — Mixed — Appeared in 2 of 14 responses Two readers raised length. One wants a shorter, more frequent format; the other is satisfied with the length but wants a summary option. This is a format preference, not a content complaint.
"The newsletter is too long. I'd rather get a shorter version twice a week." — Reader 10
Recommended Actions
Gaps in This Feedback Only 14 of your subscriber base responded, and self-selected respondents tend to be your most engaged readers. This feedback likely over-represents power users and under-represents casual readers who may have already disengaged. A broader survey or an analysis of open-rate drop-off points would complement these qualitative insights.
npx claudepluginhub ur-grue/autopunk-media-skills --plugin autopunk-media-skillsSummarises audience comments, emails, or survey responses into a structured briefing with what worked, what confused, and follow-up questions.
Synthesizes raw user interview notes, survey responses, support tickets, or feedback into key themes, pain points, unmet needs, surprises, opportunities, and confidence levels.
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".