Drafts on-brand responses to reader letters, subscriber emails, or audience complaints, matching the publication's voice while addressing the reader's specific concern or question.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autopunk-media-skills:reader-response-writerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Drafts a thoughtful, on-brand response to a reader letter, subscriber email, or audience complaint — matching the publication's voice while addressing the reader's specific concern or question.
Drafts a thoughtful, on-brand response to a reader letter, subscriber email, or audience complaint — matching the publication's voice while addressing the reader's specific concern or question.
Required: The reader's original message (full text or a close summary); the publication name and a brief description of its voice and tone (e.g., "warm and informal," "authoritative but approachable," "journalistic and direct").
Optional: The reader's name and how they should be addressed; the context of what prompted the message (which edition, article, or episode they are responding to); any factual background the response needs to account for (e.g., "the statistic they flagged was actually correct — here is the source"); the desired outcome (retain the subscriber, acknowledge and move on, invite further dialogue, issue a correction); whether the response will be private (email reply) or public (published in a letters section or read on air).
Reads the reader's message for both content and emotional register. Identifies what the reader is asking for (information, acknowledgment, correction, an apology) and how they are feeling (frustrated, curious, appreciative, hostile). The response must address both — answering the question while matching the emotional context.
Matches the publication's voice, not the reader's. If a reader writes angrily, the response does not mirror the anger — it responds in the publication's established voice. If the publication is warm and informal, the response is warm and informal even when addressing a complaint. Consistency of voice builds trust.
Addresses the specific issue directly. No generic "thank you for your feedback" filler. The response references the reader's exact point, demonstrates that it was read and understood, and provides a substantive answer. If the reader is right, the response acknowledges it. If the reader is wrong, the response corrects respectfully with evidence. If the issue is ambiguous, the response says so honestly.
Calibrates length to the situation. A simple compliment gets a warm 2-3 sentence reply. A factual correction gets a thorough response with the source. A cancellation threat gets a response that acknowledges the concern, addresses it, and makes one genuine offer — without begging. The response is as long as it needs to be and no longer.
Closes with a forward-looking note. Every response ends with something that keeps the relationship open — a question, an invitation to stay in touch, a note about upcoming content that relates to the reader's interest. This is not a sales pitch; it is a genuine gesture of continued engagement.
A complete, ready-to-send reply. Opens with a greeting using the reader's name (if provided). Body addresses the reader's message directly. Closes with a forward-looking note and sign-off. Length varies by context: 50-100 words for simple acknowledgments, 150-300 words for substantive replies, up to 400 words for sensitive or complex situations. Tone matches the stated publication voice throughout.
Reader message: "Hi — I've been a subscriber since your early days and I really value what you do. But I have to say, the last three editions have felt rushed. The analysis sections are shorter, the sourcing is thinner, and last week's piece on trade policy had two factual errors that I noticed (the tariff rate you cited for steel imports was from 2021, not 2024, and the EU commissioner you named left that role in January). I'm not trying to be difficult — I want this newsletter to stay great. But if the quality keeps slipping, I'll need to reconsider my subscription."
Publication: A paid weekly newsletter on international trade policy. Voice: authoritative, precise, appreciative of engaged readers.
Context: The editor confirms that both factual errors the reader identified are real. The last three editions were produced during a period of staff illness.
Desired outcome: Retain the subscriber. Acknowledge the errors honestly. Signal that quality is being restored.
Hi Marcus,
Thank you for writing — and for being specific. You are right on both counts. The steel tariff figure was from 2021, not the current rate, and the EU commissioner reference was outdated. We have corrected both in the archived edition and will publish a correction note at the top of this week's issue.
I will be honest with you: the last three editions were produced under difficult circumstances, and the quality did not meet our standard. That is not an excuse — it is context. You should expect the same level of rigour from every edition regardless of what is happening behind the scenes, and we fell short.
Here is what we are doing about it. We have reinstated our two-person fact-check review for every edition, effective immediately. The analysis sections will return to their usual depth starting this week — the trade policy piece on rare earth export controls will be the first test of that commitment.
Subscribers like you — the ones who catch errors and tell us — are the reason this newsletter stays honest. I genuinely appreciate it.
I hope you will give this week's edition a read and let me know if it meets the bar. Your feedback is the most useful quality check we have.
Best, The Trade Briefing Team
npx claudepluginhub ur-grue/autopunk-media-skills --plugin autopunk-media-skillsDrafts complete newsletter editions from editor's brief including opening hook, main feature, curated links, and sign-off. Helps turn raw material into polished prose quickly.
Transforms newsletter outlines into full drafts or optimizes rough drafts into publication-ready issues by orchestrating writing, auditing, and subject line skills.
Guides iterative newsletter writing from insights, ideas, or YouTube transcripts in Ben Van Sprundel's voice. Step-by-step process requiring user input at each stage.