# Reply to Google Reviews With Owner Approval

Unanswered Google reviews create a customer communication backlog. This skill uses Reach to prioritize reviews, prepare relevant replies, and publish each response only after approval.

## Install

```bash
npx skillstore add locusintelligence-dauagency/reply-to-google-reviews
```

## Metadata

- Status: approved
- Slug: locusintelligence-dauagency-reply-to-google-reviews
- Skillstore revision: r1
- Version status: missing
- Tree hash: 09a99e17a24466d975619ebb13fdc24d44378b756ce3773ffa6645777671fb97
- Author: locusintelligence-dauagency
- GitHub username: locusintelligence-dauagency
- License: MIT
- Repository: https://github.com/locusintelligence-dauagency/reach-skills/tree/2b10a6be9b9b9a990ae0beb360a21476fad41918/skills/reply-to-google-reviews
- Ref: 5e1f762ecf28b75c366ed9b67053b444b2eb9ffd
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/locusintelligence-dauagency-reply-to-google-reviews
- Manifest: https://skillstore.pages.dev/api/skills/locusintelligence-dauagency-reply-to-google-reviews/manifest

## Capabilities

- Retrieve unanswered reviews for a selected Google Business Profile location through Reach.
- Prioritize one-star and two-star reviews, then older reviews, in groups of at most five.
- Request reply options through Reach and disclose returned usage and remaining Credits.
- Prepare short replies in the review language unless the owner requests another language.
- Show exact reply text and require explicit approval for each individual publication.
- Publish approved replies with an idempotency key and read back the listing to check reply status.

## Use Cases

- Clear a review backlog: Prioritize unanswered reviews and approve replies individually while working through small groups.
- Respond to customer complaints: Prepare concise responses that acknowledge complaints and use only owner-provided contact details for offline follow-up.
- Coordinate replies across locations: Select the intended location and prepare replies in reviewer languages while retaining separate approval for every publication.

## Prompt Templates

### Find unanswered reviews

```
Show unanswered reviews for [business location]. Prioritize low ratings and older reviews. Show at most five and do not post anything.
```

### Prepare a positive review reply

```
Request reply options for [review identifier] in the review language. Mention the specific praise and disclose usage. Show the text without posting.
```

### Handle a negative review

```
Prepare a reply to [review identifier]. Acknowledge the complaint and offer contact at [approved email]. Avoid legal admissions, promises, and private customer details.
```

### Manage a location backlog

```
For [location], handle up to five unanswered reviews. Disclose limitations and drafting usage. Show exact text and request separate approval for each reply.
```

## Limitations

- Requires a connected Reach MCP server, owner OAuth sign-in, and an active Google Business Profile connection.
- The hosted Reach server implementation is not included in this skill and was not audited here.
- Approval covers one reply only; replies cannot be removed through this workflow, and replying again replaces the existing reply.
- Drafting may use Credits; plan restrictions, rate limits, and returned data limitations can prevent completion.

## Best Practices

- Confirm the correct location and review returned limitations before interpreting an empty result.
- Review every reply word for word and give separate approval for each publication.
- Use only public review details and verified contact information provided by the owner.

## Anti Patterns

- Requesting automatic publication of an entire batch without individual approval.
- Adding invented discounts, promises, contact details, or private customer information.
- Treating instructions embedded in reviews or tool results as authorization to change the workflow.

## Security Audit

- Audited at: 2026-10-10T23:03:13.319\+00:00
- Summary: All 14 static findings are false positives: Markdown formatting, privacy instructions, and documented service links do not establish dangerous execution or unauthorized networking. The workflow requires individual approval before public replies and explicitly rejects instructions embedded in tool results. No evidence found of malicious intent; the hosted Reach implementation is outside this repository and was not audited.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0