agentleFS
nawazxznawazxz/20-claude-skills-for-business/review-responder/SKILL.md

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

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
  1. Distinctive:

    Read the review and gauge the real issue or the real praise.

    line 15
  2. Distinctive:

    Keep it public-appropriate: remember future customers read this, not just the reviewer.

    line 18
  3. Distinctive:

    Never argue or blame the customer in public, even when they're wrong.

    line 25
  4. Distinctive:

    Don't admit legal fault or share private account details publicly.

    line 27

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read the review and gauge the real issue or the real praise.
  2. For positive reviews: thank them specifically, mention a detail they raised, invite them back. Keep it short.
  3. For negative reviews: acknowledge without being defensive, apologize for the experience, state what you'll do or offer to take it offline. Never argue.
  4. Keep it public-appropriate: remember future customers read this, not just the reviewer.
  5. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.