sales-online-reputation
Online reputation management strategy — monitoring reviews across Google, Yelp, Facebook, and industry sites, responding to negative reviews, generating more reviews, managing business listings, Google Business Profile optimization, reputation recovery after a crisis. Covers multi-location reputation at scale. Use when Google reviews disappeared or got removed, negative review is hurting your business, not getting enough reviews, business listings show wrong information, unsure which reputation management tool to pick, or your star rating is dropping. Do NOT use for ecommerce product review apps (use /sales-customer-reviews), B2B software reviews on G2 (use /sales-g2), or social listening for brand mentions (use /sales-social-listening).
What this skill does
# 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
2. **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
3. **How many locations?** 1, 2-10, 11-50, 50+
4. **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 Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".