agentleFS
Sign inStart free
ModernMustardSeedModernMustardSeed/local-growth-crew/skills/review-requests/SKILL.md

review-requests

Skill0 starsChanged 34 days agoMITView on GitHub

Build a review request plan for a local business: when to ask, what to say in person, the text and email to send, and the direct Google review link. Use when a business needs more reviews or a steadier flow of them.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Add a weekly routine: who sends the requests, when, and who answers new reviews within 48 hours.

    line 16
  2. Distinctive:

    Ask every customer the same way.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 requests

Business and context: $ARGUMENTS

  1. If the business is a home-service trade, run the Local Trades Kit review_request_timing tool with the trade, the job type and, if given, the completion date. Use its windows and wording. For any other business, ask at the moment the customer first sees the result or says thank you.
  2. Write three pieces:
    • The in-person ask: one or two sentences the owner or crew says at completion.
    • A text message under 300 characters with the review link.
    • An email under 100 words with the review link.
  3. The review link is https://search.google.com/local/writereview?placeid=<PLACE_ID>. Tell the user how to find their Place ID with Google's Place ID Finder. Never guess it.
  4. Add a weekly routine: who sends the requests, when, and who answers new reviews within 48 hours.

Ask every customer the same way. No filtering for happy customers first, and no discounts or gifts for reviews. No em dashes.

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.

Check your setup, free