review-responder
Skill0 starsChanged 3 months agoMITView on GitHub
Write a reply to a public customer review, positive or negative. Use when someone pastes a Google, Yelp, app store, or marketplace review and needs a professional public response.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- alumpe/skillstheir own version, first seen Nov 8, 2026
- ARCASSystems/FounderOStheir own version, first seen Oct 24, 2026
- buildwithreef/claude-skillstheir own version, first seen Jul 2, 2026
- Ootto-AI/claude-support-skillstheir own version, first seen Jun 12, 2026
- emd-ai/trades-claude-skillstheir own version, first seen Mar 1, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- ARCASSystems/FounderOS★ 7same name
- emd-ai/trades-claude-skills★ 2same name
- Ootto-AI/claude-support-skills★ 1same name
- alumpe/skills★ 0same name
- buildwithreef/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- ad-copySkill
- blog-writerSkill
- cold-outreachSkill
- content-repurposerSkill
- contract-summarizerSkill
- crm-note-cleanerSkill
- data-cleanerSkill
- expense-summarySkill
- faq-builderSkill
- follow-up-emailSkill
- invoice-builderSkill
- lead-qualifierSkill
- meeting-notesSkill
- newsletter-writerSkill
- proposal-writerSkill
- social-post-packSkill
- sop-writerSkill
- support-replySkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Read the review and gauge the real issue or the real praise.
- Distinctive: line 18
Keep it public-appropriate: remember future customers read this, not just the reviewer.
- Distinctive: line 25
Never argue or blame the customer in public, even when they're wrong.
- Distinctive: line 27
Don't admit legal fault or share private account details publicly.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review Responder
A public reply that helps the reviewer and reads well to everyone else watching.
Inputs needed
- The review text and its rating.
- (Optional) The business name, any facts about what happened, and how you'd like to make it right.
Steps
- Read the review and gauge the real issue or the real praise.
- For positive reviews: thank them specifically, mention a detail they raised, invite them back. Keep it short.
- For negative reviews: acknowledge without being defensive, apologize for the experience, state what you'll do or offer to take it offline. Never argue.
- Keep it public-appropriate: remember future customers read this, not just the reviewer.
- Sign off as the business.
Output format
A ready-to-post reply. For negative reviews, add a one-line internal note on what to verify or offer before posting.
Voice & rules
- Never argue or blame the customer in public, even when they're wrong.
- Be specific; a copy-paste "sorry to hear that" reads worse than nothing.
- Don't admit legal fault or share private account details publicly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

