Google Business Review Responder

v1.0.0

Monitors new Google Business reviews, drafts tailored responses sent via Telegram for operator approval before posting publicly.

0· 56·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
Requires OAuth token
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (monitor GBP reviews, draft replies, and send via Telegram for approval) matches the code: gbp_reviews.py polls Google APIs and can post replies. The skill legitimately needs OAuth client credentials and refresh tokens saved per-client. One mismatch: there is no built-in Telegram integration in the code—SKILL.md expects the OpenClaw agent to send the draft messages via an existing Telegram channel. This is a design choice (agent handles messaging) but worth noting.
Instruction Scope
SKILL.md instructs the agent to run the included scripts, save pending review JSON files, send drafts via Telegram, and only post after operator approval. The code only accesses client config files and Google APIs and writes pending and log files in its workspace; it does not read unrelated system files or exfiltrate data to unknown endpoints. HIPAA rules are explicitly included in the guidelines.
Install Mechanism
No install spec is provided (instruction-only skill). The included Python scripts declare standard pip dependencies (google-auth, google-auth-oauthlib, requests, Flask optionally). There are no downloads from untrusted URLs or unusual install steps in the package.
Credentials
The skill does not request environment variables but does require per-client OAuth credentials (oauth_client_id, oauth_client_secret, and long-lived refresh_token) stored in clients/*.json. Those credentials are sensitive but are necessary for the stated purpose. Ensure you understand that refresh tokens allow ongoing API access until revoked and are saved in plaintext files by the scripts.
Persistence & Privilege
Skill does not set always:true and does not alter other skills. It will create files in its workspace (clients/, pending/, review_log.json) which is normal for its function. Note: the platform's autonomous invocation (default) could run the 'check' flow on heartbeat; the skill and scripts rely on operator approval before calling the reply flow—if an agent or operator misconfigures automation to call the reply command without approval, replies could be posted. That is operational risk, not intrinsic malicious behavior in the skill.
Assessment
This package is coherent for managing Google Business reviews, but review the following before installing: - OAuth credentials and refresh tokens: The skill requires storing oauth_client_id, oauth_client_secret, and a long-lived refresh_token per client in plaintext files under the skill workspace (clients/*.json). Treat these as sensitive: restrict filesystem access, use correct permissions, and rotate/revoke tokens if compromised. - Telegram messaging: The scripts do NOT send Telegram messages themselves—you must have OpenClaw configured to send the drafted messages and to enforce the manual approval step. Verify your agent's heartbeat/automation will not auto-run the 'reply' command without human confirmation. - OAuth server: oauth_server.py is a convenience to capture refresh tokens remotely. If you expose it on a public VPS, run it under HTTPS and secure the server; by default the code sets OAUTHLIB_INSECURE_TRANSPORT to allow HTTP which is insecure. Prefer get_client_token.py run locally if you cannot secure a web server. - File writes: The skill creates pending/ and review_log.json in its workspace. Ensure the workspace location is appropriate and protected; do not place it in a path readable by untrusted users or bots. - Verify code yourself: This is a community-provided skill (source unknown). If you plan to run it in production, audit the Python code and consider storing tokens in a secret manager rather than plaintext files. If you trust the source and follow the operational cautions above (secure storage, HTTPS for onboarding server, agent-level checks to prevent auto-posting), the package is appropriate for its stated purpose.

Like a lobster shell, security has layers — review code before you run it.

business-profilevk97fweqwpt8wzgaz2sz71vgck584q11egbpvk97fweqwpt8wzgaz2sz71vgck584q11egooglevk97fweqwpt8wzgaz2sz71vgck584q11ehipaavk97fweqwpt8wzgaz2sz71vgck584q11elatestvk97fweqwpt8wzgaz2sz71vgck584q11ereviewsvk97fweqwpt8wzgaz2sz71vgck584q11etelegramvk97fweqwpt8wzgaz2sz71vgck584q11e

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments