agentleFS
Sign inStart free
postproxypostproxy/postproxy-claude-plugin/skills/google-business/SKILL.md

google-business

Skill0 starsChanged 2 months agoMITView on GitHub

Manage a Google Business Profile via Postproxy. Use when the user wants to edit their Google business listing (name, description, hours, photos, attributes, services, food menus, action links) or read and reply to Google reviews.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call profiles_list and pick the google_business profile if it isn't known.

    line 8
  2. Very specific:

    Call profiles_placements — each location is returned as a full path accounts/X/locations/Y.

    line 9

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

Manage a Google Business Profile location — the business listing itself, not posts (posts go through /postproxy:publish).

Resolve the location first:

  1. Call profiles_list and pick the google_business profile if it isn't known.
  2. Call profiles_placements — each location is returned as a full path accounts/X/locations/Y. That's the location_id every tool needs.

Read before you write. Google's updates are field-masked and replace named fields wholesale (no merge). Fetch the current object, edit it, patch it back. Confirm destructive edits.

  • Business info: google_business_location_get → google_business_location_update. The fields list names exactly what's being replaced; anything named but omitted is cleared. Categories are resource names (categories/gcid:...) resolved via google_business_categories_list (needs region_code; filter searches by display name).
  • Hours: google_business_hours_update — each named block (regularHours/specialHours/moreHours) is replaced entirely.
  • Attributes: always call google_business_attributes_available first (valid set + value types depend on category/region), then google_business_attributes_update matching each valueType (BOOL→values, URL→uriValues, ENUM→repeatedEnumValue). Read with google_business_attributes_get.
  • Media: google_business_media_list; google_business_media_create fetches from a public https URL (min 250×250, ≤5MB); google_business_media_delete by resource name.
  • Action links: google_business_place_action_links_list / _create / _update / _delete; accepted place_action_type varies by category.
  • Services & food menus: google_business_service_list_get/_update and google_business_food_menus_get/_update are full replacements gated on metadata.canModifyServiceList / canHaveFoodMenus (422 = unsupported for this location).

Reviews (profile-scoped, not on a post):

  • profile_comments_list (optional placement_id filters to one location); reviews sync twice daily (06:00 & 18:00 UTC). Inspect one with profile_comments_get.
  • Reply only — profile_comments_create with parent_id (the review) + text; no top-level comments; publishes async (pending→published/failed).
  • profile_comments_delete removes only your reply; the review itself can't be deleted.

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