review-response-writer — Claude Code skill for review replies
The review-response-writer Claude Code skill drafts review replies in the owner’s voice and sorts reviews by situation. It flags mentions of injury, illness, discrimination, or legal threats for the owner.
MIT 110 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill review-response-writer -a claude-codeWhat review-response-writer does
The skill reads review text and drafts a reply that matches the owner’s usual tone. For its first run, provide past replies or a note describing how the owner speaks. It handles praise, complaints, disputed accounts, and suspected fake reviews with different response approaches. Complaint drafts can also move the conversation to a private channel.
Reviews mentioning injury, illness, discrimination, legal threats, or accusations naming an employee are flagged for the owner instead of receiving a final draft. The skill can prepare platform removal-request steps for suspected fakes and spot recurring issues across a batch. Positive replies stay under 100 words and negative ones under 150; its suggested cadence for negative reviews is 24-48 hours.
What it helps with
- draft a specific reply to a positive review
- respond to a complaint without arguing in public
- correct a factual claim in a review briefly
- flag a suspected fake and prepare removal-request steps
- spot recurring issues across a review backlog
Example prompts for the agent
- Reply to this review in the owner’s voice: [review text]
- Sort this review export, draft replies, and flag cases for the owner
- Handle this 1-star review and assess whether a removal request is warranted
How to install review-response-writer
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill review-response-writer -a claude-code2Manually: put the files in place
~/.claude/skills/review-response-writer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/review-response-writer/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill review-response-writer -a codex2Manually: put the files in place
.agents/skills/review-response-writer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill review-response-writer -a cursor2Manually: put the files in place
.cursor/skills/review-response-writer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills review-response-writer2Manually: put the files in place
.github/skills/review-response-writer/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill review-response-writer -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path review-response-writerManually: put the files in place
.devin/skills/review-response-writer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill review-response-writer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about review-response-writer
How do I install review-response-writer in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill review-response-writer -a claude-code. The skill file is at ~/.claude/skills/review-response-writer/SKILL.md.
What does review-response-writer do?
It sorts reviews by situation and drafts replies in the owner’s voice. It flags serious accusations and legal or medical issues for the owner.
What should I provide for the first run?
Provide the review text. To match the owner’s voice, include some past replies or a note about their writing style.
Source text
SKILL.md · MIT
---
name: review-response-writer
description: Respond to Google, Yelp, and industry reviews in the owner's voice -- gracious on the 5-stars, masterful on the 1-stars. Handles the angry customer, the unfair review, the fake review, and the one that mentions a legal or health issue. Every response written for the thousand future customers reading it.
tools: Read, Write, Bash, WebFetch
model: inherit
---
# Review Response Writer
The response to a bad review is not for the reviewer -- it is for every prospect who reads it for the next five years. Input: the review text (pasted, exported, or fetched from the profile), and on first run a few existing responses or a note on how the owner talks. Output: responses ready to post, plus escalation flags for the ones that need more than words.
## Workflow
1. **Learn the voice.** From past responses or the owner's description: warmth level, formality, sign-off style, whether they use names. Small-business responses that sound like the actual owner outperform corporate-polished ones -- keep contractions, keep personality.
2. **Triage each review:**
- `GLOW` (4-5 stars) -- thank specifically (echo the detail they praised, never generic), reinforce the service mentioned (it is searchable text), invite them back.
- `LEGITIMATE COMPLAINT` -- acknowledge the specific failure without excuses, state the fix made, take it offline with a real contact, never argue. No coupons in public (it trains complaint-for-discount).
- `UNFAIR/MISTAKEN` -- correct the record factually and briefly ("Our records show we honored the quoted price of...") while staying gracious; readers can tell who is being reasonable.
- `SUSPECTED FAKE` (no record of the customer, competitor patterns) -- respond once, neutrally ("We have no record of serving you -- contact us and we'll make it right"), and output the platform's removal-request steps with the policy grounds.
- `ESCALATE` -- anything mentioning injury, illness, discrimination, legal threats, or an employee by name in an accusation: draft nothing final; flag for the owner and, where serious, counsel, with a holding-pattern response option.
3. **Draft.** Responses under 100 words for positives, under 150 for negatives. Vary structure across a batch -- ten identical-template responses read as a bot and undo the effort.
4. **Batch report.** For a backlog: respond oldest-negative first (unanswered negatives do compounding damage), then recent positives. Note patterns worth fixing upstream -- three reviews mentioning wait times is an operations finding, not a writing task.
## Rules
- Never admit legal fault, discuss health/medical specifics, or confirm someone was a customer on platforms where that itself is sensitive (medical, legal, financial services -- respond without confirming the relationship).
- Never argue, never sarcasm, never match the reviewer's temperature. The audience is the reader, not the reviewer.
- Specificity is the tell of sincerity: echo one concrete detail from every review; a response that could sit under any review helps nobody.
- Public forgiveness, private resolution: the public reply shows character, the offline contact fixes the problem.
- Fake-review accusations stay out of the public response -- neutrality publicly, evidence in the removal request.
- Response velocity matters: recommend responding to negatives within 24-48 hours and set that as the standing cadence.
## Quick Commands
- "Respond to this review" -- single review, voice-matched
- "Clear my backlog [export/profile]" -- triaged batch with drafts
- "Handle this 1-star" -- deep treatment: response + offline script + removal assessment if warranted
- "What are my reviews telling me?" -- the upstream operations patterns
© OneWave-AI · MIT · OneWave-AI/claude-skills