review-response

review-response is a skill for Claude Code, Codex from GTMify/aigtm. It costs 67 tokens per session (1,178 once invoked), scanned A, original, MIT.

A writing assistant for replies to public customer reviews on sites such as Google, Yelp, and Trustpilot.

In plain words
What is it for?
Drafting positive and negative review responses in the business's voice, including replies to complaints, suspected fake reviews, and difficult situations.
Why use it?
It helps businesses answer praise or complaints clearly while considering the reviewer, future customers, and each site's rules.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Drafting positive and negative review responses in the business's voice, including replies to complaints, suspected fake reviews, and difficult situations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gtmify/aigtm/review-response
View source ↗ GTMify/aigtm
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add GTMify/aigtm --skill review-response
Clone the repo
git clone --depth 1 https://github.com/GTMify/aigtm

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for review-response

README.md
[![agentmods](https://agentmods.dev/badge/skills/gtmify/aigtm/review-response/github.svg)](https://agentmods.dev/skills/gtmify/aigtm/review-response)
Your own site
<a href="https://agentmods.dev/skills/gtmify/aigtm/review-response"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/review-response/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for review-response

Your own site · 80×15
<a href="https://agentmods.dev/skills/gtmify/aigtm/review-response"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/review-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,178 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.01178
Opus 5.5 $0.00027 $0.00471
Sonnet 5.5 $0.00013 $0.00236
Haiku 4.5 $0.00007 $0.00118

Measured 1mo ago against content hash 4db0ef3bc578, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-response scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/review-response/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Read the full file on GitHub · 108 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 108 lines · 67 tokens per session scan A 4db0ef3bc578

Subscribe to this mod's changes

review-response is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 23d ago), licensed MIT. It adds 67 tokens to every session and 1,178 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

activity-capture-diagnostic

Diagnose sales activity capture quality across a team and grade it A through F. Computes per-rep capture rate, under-loggers below team median, phantom-progression opportunities (stage advanced with zero logged activity), activity type mix, and the correlation between capture rate and win rate. Use when the user asks…

elijeangilles/revops-skills · 93 tokens

lead-routing-rule-analyzer

Diagnose lead routing health and grade it A through F. Computes speed-to-lead (creation-to-assignment and assignment-to-first-touch) with percentiles, SLA violations, orphaned leads, distribution imbalance across reps, and routing leakage (assigned rep territory does not match lead territory). Use when the user asks…

elijeangilles/revops-skills · 95 tokens

salesforce-revops-audit

Run a comprehensive Salesforce RevOps health audit across five dimensions (pipeline health, data quality, forecast hygiene, deal integrity, process integrity) and produce a graded report (A through F) with a prioritized remediation queue. Use as the entry point for any new Salesforce org assessment, before a new…

elijeangilles/revops-skills · 98 tokens

deal-investigator

Produce a structured deal review for a single opportunity. Pulls activity, stage progression, comparable deals, and risk indicators. Use when a manager needs to pressure-test a specific deal, prepare for a deal review, decide whether to escalate, or determine if a deal is real before the forecast call.

elijeangilles/revops-skills · 63 tokens

forecast-call-prep

Prepare the executive summary for a weekly forecast call by reconciling rep commits against historical close-rate models and surfacing material variance. Use when the user asks for forecast call prep, weekly forecast review, forecast variance analysis, or a Monday morning forecast memo.

elijeangilles/revops-skills · 56 tokens

pipeline-hygiene-audit

Audit a sales team's open pipeline for hygiene issues and produce a per-rep punchlist of fixes ranked by severity. Use when the user asks for pipeline hygiene, data quality check, stale opp report, pipeline cleanup, or CRM cleanup before a forecast call or QBR.

elijeangilles/revops-skills · 61 tokens