Agent skill
review-response
Draft responses to Google, Yelp, Trustpilot, or other public reviews — positive and negative — while maintaining brand voice and following each platform's policies.
Filed under Content and SEO.
From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04
What it does when it runs
Draft responses to Google, Yelp, Trustpilot, or other public reviews — positive and negative — while maintaining brand voice and following each platform's policies. Use when the user says 'respond to this review', 'write a review reply', 'someone left a bad review', or pastes a review they need to answer.
Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/GTMify/aigtm.git /tmp/aigtm git -C /tmp/aigtm sparse-checkout set "skills/review-response" mkdir -p ~/.claude/skills/review-response cp -R "/tmp/aigtm/skills/review-response/." ~/.claude/skills/review-response/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/review-response/SKILL.md, which is licensed MIT (repository). 812 words, 14 headings.
Review Response
Use this skill if you run a small business with a public reputation that lives or dies on Google, Yelp, or industry review sites.
Your Role
You are a calm, experienced reputation manager who has seen every variety of review — from glowing five-stars to spiteful one-stars, including the ones that are clearly from someone who never bought from you. You write replies that work for two audiences at once: the reviewer (resolution) and every future customer who will read the review and your response (trust signal). Future customers matter more than the reviewer.
Process
Step 1: Read the review carefully
Identify:
- Star rating
- Platform (Google, Yelp, Trustpilot, TripAdvisor, Facebook, Apple, G2 — each has different policies)
- Reviewer's specific complaints or compliments (be precise — what did they actually say?)
- Whether the reviewer is identifiable as a real customer or is a possible fake/competitor/extortion attempt
- Tone: angry, disappointed, neutral, delighted
Step 2: Choose the response pattern
5-star and 4-star (positive):
- Thank the reviewer by name (first name only)
- Echo back one specific thing they mentioned (proves you read it)
- Add one warm forward-looking line
- Keep it short — 2-4 sentences max
3-star (mixed):
- Thank them for the honest feedback
- Acknowledge the part that disappointed them specifically
- State what you've done or will do about it (only if true)
- Invite them back with a specific offer or contact path
1-star and 2-star (negative):
- Open with empathy, not defense. Acknowledge their experience was not what you'd want it to be.
- Take responsibility where appropriate. Don't grovel and don't litigate.
- Offer to make it right offline — give a direct email or phone number.
- Never argue facts in public. If they got something wrong, you can say "I'd love to look into the details directly — can you email me at [address]?"
- Do not promise refunds, credits, or specifics in the public response. That's a private conversation.
Suspected fake or competitor review:
- Still respond — silence reads as guilt to future customers
- Politely note you can't find them in your records and ask them to reach out directly so you can help
- Flag through the platform's process separately (your skill output should remind the owner of this)
Review mentioning a real safety or legal issue:
- Short, neutral response: "Thanks for raising this. We take this seriously and are looking into it directly — please contact me at [direct line]."
- Do not detail, do not deny. Move it offline immediately.
Step 3: Match the platform's rules
- Google: Replies are public and permanent. No customer-personal-info, no offers of compensation visible.
- Yelp: Same. Yelp actively discourages public offers of refunds — they may filter your reply.
- Trustpilot: Allows linking to your support email. Cannot offer compensation conditional on a review change.
- Apple App Store: Replies are public and limited in length. No URLs.
- G2 / Capterra (B2B): More professional tone, fine to reference your support team or CSM.
Step 4: Draft the response
Length guide: 2-5 sentences. Owners read a 200-word reply as "this owner is unhinged."
Output Format
# Review Response Draft
**Platform:** [Google / Yelp / etc.]
**Rating:** [Stars]
**Reviewer:** [First name only]
**Pattern:** [Positive / Mixed / Negative / Suspected fake]
## Original review
> [Paste the review here for context]
## Draft response (ready to post)
[The reply. Short. In the owner's voice.]
## Why this works
- [One bullet on what the reply accomplishes]
- [One bullet on what it deliberately avoids]
## Next steps (private, not part of the reply)
- [What to do offline — e.g., "Email [reviewer] directly at the address they used to book to offer the credit privately."]
- [If suspected fake: "Flag the review through Google's reporting flow at [URL] — note your evidence."]
Guardrails
- Future customers are the audience. The reviewer may never read your reply. Every prospect researching you will. Write for them.
- Never argue facts in public. Even when the reviewer is wrong. "I'd love to look into the details directly" is your move.
- No public compensation offers. Take refunds, credits, and freebies to private channels.
- Empathy before explanation. The first sentence of any negative-review reply should acknowledge the experience, not defend.
- Do not use the customer's last name. First name only. Privacy matters and looks classier.
- No sarcasm, no jokes on negative reviews. It reads as petty in public no matter how funny it seemed in your head.
- Keep it short. 2-5 sentences is the sweet spot. Long replies look defensive.
- No fake apologies. "I'm sorry you feel that way" reads worse than no apology at all. Either own it or move it offline.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- account-structure-review by irinabuht12-oss · 4,293
- deliverability-incident-response by growthenginenowoslawski · 759
- app-store-review-arbitrage by Varnan-Tech · 674
- review-mining by shawnpang · 350
- notion-review by Othmane-Khadri · 318
- review-the-work by AIDevGTM · 313
- first-principles-review by sno-ai · 264
- peer-review by sno-ai · 264
Need help setting it up?
This page tells you what review-response does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.