Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

sales-online-reputation销售网络声誉

Agent Skill

sales-online-reputation 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

367

周安装

15

GitHub Stars

13

下载量

119
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:sales-online-reputation(销售网络声誉)
来源仓库:https://github.com/sales-skills/sales
仓库路径:skills/sales-online-reputation
安装命令:
npx skills add https://github.com/sales-skills/sales --skill sales-online-reputation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/sales-skills/sales --skill sales-online-reputation

简介

销售网络声誉用于查找、检索和筛选相关信息。

  • 适用于品牌舆情监测、负面评论应对和口碑建设指导。
  • 支持多平台评价抓取与情感倾向分析。sales-online-reputation 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 使用前应获得授权访问公开评论数据。
  • 建议制定分级响应策略并按优先级处理紧急事件。

SKILL.md

Online Reputation Management Strategy

Helps the user monitor, manage, and improve their online reputation — from collecting more reviews and responding to negative feedback through managing business listings, handling reputation crises, and choosing the right ORM tools.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

  1. What do you need help with?

- A) Getting more reviews - B) Responding to a negative review - C) Reviews disappeared or were removed - D) Business listings show wrong information - E) Choosing a reputation management tool - F) Reputation recovery after a crisis or PR issue - G) Multi-location reputation management at scale - H) Google Business Profile optimization - I) Something else — describe it

  1. What type of business?

- A) Healthcare / dental - B) Home services (plumbing, HVAC, roofing, etc.) - C) Automotive - D) Restaurant / hospitality - E) Retail / multi-location - F) Professional services (legal, financial, real estate) - G) SaaS / B2B (→ probably /sales-g2 or /sales-trustpilot instead) - H) Other

  1. How many locations? 1, 2-10, 11-50, 50+
  2. Current tools? Birdeye, Podium, Yext, BrightLocal, NiceJob, Reputation.com, none, other

If the user's request already provides enough context, skip to the relevant step.

Step 2 — Route or answer directly

If the request maps to a platform-specific skill, route:

  • Birdeye platform questions → /sales-birdeye {your question}
  • Trustpilot-specific questions → /sales-trustpilot {your question}
  • G2/B2B software reviews → /sales-g2 {your question}
  • Customer feedback surveys (NPS, CSAT) → /sales-customer-feedback {your question}
  • Ecommerce product reviews → /sales-customer-reviews {your question}
  • Social media monitoring → /sales-social-listening {your question}

Otherwise, answer directly using the strategy guidance below.

Step 3 — Reputation management strategy

Read references/platform-guide.md for detailed ORM strategy — review generation tactics, response templates, listings management, tool comparison, Google Business Profile optimization, crisis response playbook, and multi-location management.

Answer the user's question using only the relevant section.

Step 4 — Actionable guidance

You no longer need the strategy guide — focus on the user's specific situation.

Key decision points:

  • Review generation: SMS requests within 1 hour > email requests. Personalize with staff name. Don't incentivize (Google prohibits it).
  • Response strategy: Respond to all reviews within 24-48 hours. Negative reviews: empathize, take offline, offer resolution. Positive reviews: thank briefly, reinforce what they liked.
  • Tool selection: Single location → NiceJob or Broadly. Multi-location → Birdeye or Podium. Enterprise → Reputation.com or Yext.
  • Listings: NAP consistency is foundational. Fix Google Business Profile first, then cascade to other directories.
  • Crisis: Don't delete or argue. Respond publicly, take offline, fix the root cause, then bury negative content with positive review volume.

If you discover a tip not covered in references/learnings.md, append it there.

Gotchas

*Best-effort from research — review these, especially items about Google policies that change frequently.*
  • Google prohibits incentivized reviews. No discounts, freebies, or rewards in exchange for reviews. Violations can get all your reviews removed.
  • Review gating violates Google policy. Don't pre-screen customers and only send satisfied ones to Google. Send everyone the same review link.
  • Google reviews disappear without warning. In Feb 2026, thousands of businesses lost reviews due to a Google display bug. Also, Gemini AI integration into review moderation caused 600%+ spike in deletions Jan-Jul 2025.
  • You can't delete negative reviews. You can only flag reviews that violate Google's policies (spam, off-topic, conflicts of interest). Most flagged reviews are not removed.
  • ORM tools don't own your listings. They sync data to directories, but Google/Yelp/Facebook can override with user-submitted edits at any time.
  • "Reputation management" vs "reputation repair" are different industries. ORM is ongoing monitoring and review generation. Reputation repair is suppressing negative search results — that's a different (expensive) service.

Before recommending a specific platform skill

This skill covers a strategy domain across many platforms. Before pointing the user to any specific platform skill (any /sales-{platform} listed in ## Related skills, e.g., /sales-mailshake, /sales-klaviyo, /sales-apollo), read that platform skill's actual SKILL.md first. The 1-line description in ## Related skills is enough to *identify* a candidate — it's not enough to *commit* to it or to write a prompt that invokes it well.

How to read it:

  • If ~/.claude/skills/{skill-name}/SKILL.md exists locally, Read it.
  • For sales-* skills, WebFetch directly from this repo: https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md — e.g., for sales-mailshake: https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md.
  • For non-sales-* skills (third-party), look up {org}/{repo} in ~/.claude/skills/sales-do/references/skill-sources.md if installed and fetch the same skills/{skill-name}/SKILL.md path under that repo.

After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its argument-hint shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's argument-hint. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.

Related skills

  • /sales-birdeye — Birdeye platform help (reviews, listings, messaging, surveys for multi-location). Install: npx skills add sales-skills/sales --skill sales-birdeye
  • /sales-trustpilot — Trustpilot platform help (TrustBox widgets, TrustScore, Google Seller Ratings). Install: npx skills add sales-skills/sales --skill sales-trustpilot
  • /sales-g2 — G2 platform help (B2B software reviews, buyer intent data). Install: npx skills add sales-skills/sales --skill sales-g2
  • /sales-customer-reviews — Product review collection strategy for ecommerce. Install: npx skills add sales-skills/sales --skill sales-customer-reviews
  • /sales-customer-feedback — Customer feedback, NPS, CSAT strategy. Install: npx skills add sales-skills/sales --skill sales-customer-feedback
  • /sales-social-listening — Social listening and brand monitoring. Install: npx skills add sales-skills/sales --skill sales-social-listening
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do

Examples

Example 1: "I got a 1-star Google review from an angry customer who says we damaged their car. What do I do?" → Respond publicly within 24 hours: acknowledge their frustration, apologize for the experience, and ask them to contact you directly to resolve it. Don't argue facts publicly. After resolving offline, ask if they'd consider updating their review. Then increase review request volume to dilute the negative with fresh positives.

Example 2: "I have 15 auto repair locations and our Google ratings vary from 3.2 to 4.8. How do I bring the low performers up?" → Benchmark review volume and recency per location. Low-rated locations usually have low volume (a few bad reviews dominate). Implement automated SMS review requests at every location with consistent timing. Identify common complaints at low-rated locations (from review text) and fix operational issues. Set up location-level dashboards so managers see their own metrics.

Example 3: "Which reputation management tool should I use for my 3 dental offices?" → For 3 locations in healthcare, Birdeye is the strongest fit — it has native Dentrix/Open Dental integrations, HIPAA compliance, and healthcare-specific review site monitoring (Healthgrades, Vitals, RateMDs). Alternative: Podium if your priority is SMS-first patient communication over review breadth.

Troubleshooting

Google reviews disappeared overnight

  • Check if this is a known Google bug (common in late 2025/early 2026). Wait 48-72 hours — display bugs usually self-resolve.
  • If reviews are permanently removed, they likely triggered Google's AI spam filter. Common triggers: reviews from the same IP, incentivized reviews, reviews from accounts with no other activity.
  • File a Google Business Profile support request through the GBP Help Community or Google support chat.

Star rating dropping despite good service

  • Check if unhappy customers are finding you on Google while happy ones aren't being asked. Automate review requests to ALL customers, not just ones you think are satisfied.
  • Look for patterns in negative reviews — if multiple mention the same issue (wait times, billing, staff attitude), that's an operational problem, not a reputation problem.
  • Check review velocity — a sudden spike in negative reviews with similar language could be a competitor or disgruntled ex-employee. Flag for Google review.

Business listings show wrong hours/address/phone

  • Start with Google Business Profile — verify ownership, correct the data, and publish.
  • Check for duplicate listings on the same platform — duplicates confuse both customers and aggregators.
  • Use an ORM tool (Birdeye, Yext, BrightLocal) to push correct data to all directories at once. Manual updates to 50+ directories are impractical.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.14%
按下载量换算43

Claude

29.93%
按下载量换算36

Cursor

21.19%
按下载量换算25

Gemini CLI

9%
按下载量换算11

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills