Token导航 LogoToken导航TokenDH.com
效率只读clawhub未标认证来源可访问clear审计通过

google-review-responderGoogle 审查 responder

Agent Skill

google-review-responder 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,869

周安装

122

GitHub Stars

公开资料未说明

下载量

1,005
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:google-review-responder(Google 审查 responder)
来源仓库:https://github.com/chris-openclaw/google-review-responder
安装命令:
openclaw skills install google-review-responder
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install google-review-responder

简介

监控新的 Google Business 评论,起草通过 Telegram 发送的定制回复,供运营商批准,然后再公开发布。

SKILL.md

Skill: Google Business Review Responder

Description

Automatically monitors Google Business Profile reviews for clients, drafts professional responses, and sends them via Telegram for approval before posting.

Trigger

This skill activates during heartbeat checks and when the operator replies to a review approval message.


Review Check Flow (Heartbeat)

  1. Run the review check script for each configured client:
   python3 ~/review-responder/gbp_reviews.py check --client <client_id>
  1. For each new unanswered review found, draft a response following the Response Guidelines below.
  2. Send the draft to the operator via Telegram in this format:
📝 New Review for [Business Name]

⭐ [star_rating] from [reviewer_name]
💬 "[review comment]"

My draft reply:
"[your drafted response]"

Reply OK to post, or send your edits.
(Review ID: [review_id] | Client: [client_id])
  1. Do NOT post the reply automatically. Wait for operator approval.

Approval Flow (Chat)

When the operator replies to a review draft:

  • "OK" or "post it" or "send it" or "approved": Post the draft as-is using:
  python3 ~/review-responder/gbp_reviews.py reply --client <client_id> --review <review_id> --reply "the approved response"

Confirm once posted: "Done -- reply posted for [reviewer_name]'s review."

  • Edited text: If the operator sends replacement text (anything that isn't a simple approval), use their text as the reply instead. Confirm before posting: "Got it -- posting your version now."
  • "Skip" or "ignore": Do not reply to that review. Remove it from pending.

Response Guidelines

Tone Principles

  • Warm, professional, and human -- not corporate or robotic
  • Specific to what the reviewer said (never generic "thanks for your review!")
  • Concise: 2-4 sentences max
  • Match the energy of the review without being over the top

By Star Rating

5 Stars:

  • Thank them warmly and reference something specific they mentioned
  • Reinforce what they loved ("We're glad [specific thing] made a difference")
  • End with a light invitation to return or share with others
  • Keep it brief -- don't overdo it on a great review

4 Stars:

  • Thank them and acknowledge specific positives
  • If they mentioned something that could improve, acknowledge it gracefully without being defensive
  • Show you're listening: "We appreciate the feedback on [topic] and are always looking to improve"

3 Stars:

  • Thank them for taking the time
  • Acknowledge both the positives and the concern
  • Show genuine interest in making it right: "We'd love the chance to do better next time"
  • Optionally invite them to reach out directly

1-2 Stars:

  • Lead with empathy, not defensiveness: "We're sorry to hear this wasn't the experience you deserved"
  • Acknowledge the specific issue without making excuses
  • Offer a path forward: invite them to contact the business directly
  • Keep it short and dignified -- do not argue or over-explain
  • Never blame the reviewer or question their experience

HIPAA Compliance (CRITICAL)

  • NEVER reference or confirm any medical conditions, diagnoses, treatments, medications, or health details -- even if the reviewer mentioned them in their review
  • NEVER confirm or deny that someone is or was a patient
  • Keep responses general: "your experience," "your visit," "your care" -- not "your diagnosis" or "your treatment"
  • If a reviewer shares health details in their review, do NOT reference those specifics in the reply. Respond to the sentiment and experience only.
  • When inviting someone to follow up, use "please contact our office" -- never suggest discussing their "case" or "medical records"
  • This applies to ALL star ratings, positive and negative

Things to Avoid

  • Generic filler: "We value all our customers" / "Your feedback is important to us"
  • Mentioning the star rating directly: "Thanks for the 5 stars!"
  • Being defensive about negative reviews
  • Making promises the business can't keep
  • Using the reviewer's full name unless they used it in their review
  • Emojis (unless the business brand is very casual and the operator approves it)
  • Referencing any health information, even if the patient shared it publicly (HIPAA)

Checking Pending Reviews

To see what's waiting for approval:

python3 ~/review-responder/gbp_reviews.py pending

Dependencies

  • Python 3 with: google-auth, google-auth-oauthlib, requests
  • Client config files in ~/review-responder/clients/
  • Telegram channel connected for approval messages

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

81.09%
按下载量换算815

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills