[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVS3MBVNC66WY8SWHPBESS":3,"skill-same:01M7EVS3MBVNC66WY8SWHPBESS":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EVS3MBVNC66WY8SWHPBESS","review-manager",null,"Manage online reviews — generation strategies, response playbooks, reputation monitoring, and turning reviews into growth.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-review-manager\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: review-manager\ndescription: Manage online reviews — generation strategies, response playbooks, reputation monitoring, and turning reviews into growth.\ncategory: business-marketing\n---\n\n## Overview\n\nReviews are modern word-of-mouth: they drive local SEO, purchase decisions, and trust. This skill covers the full review practice — generating authentic reviews at scale, responding to positive and negative reviews, monitoring reputation across platforms, and using review insights to improve the business.\n\n\nReviews are the new word-of-mouth at scale: 90%+ of buyers read them, and star ratings directly move conversion. Review management is both defensive (responding to negatives, catching fake reviews) and offensive (generating authentic positives systematically). It is a compounding asset — every review works for you indefinitely.\n## When to use\n\n- Increasing review volume and ratings\n- Responding to negative reviews\n- Building a review generation system\n- Monitoring brand reputation\n- Improving local search via reviews\n- Turning reviews into marketing assets\n\n- Recovering from a negative review crisis\n- Building review generation into the customer journey\n- Monitoring brand sentiment across platforms\n- Managing reviews across 100+ locations\n- Responding to viral negative incidents\n- Building review programs for B2B services\n## Core concepts\n\n**The review funnel.** Ask → make it easy → follow up → respond → showcase. Most happy customers never review unless asked; most unhappy ones review unprompted. Systematic asking corrects the negativity bias.\n\n**Asking well.** Timing (right after positive moments: delivery, successful support, 5-star NPS), channel (email, SMS, in-app, in-person with QR codes), and simplicity (direct links to the right platform, no multi-step processes). Never incentivize with payments for positive reviews — it's against most platforms' policies and often illegal; you can incentivize honest reviews in some contexts, but check platform rules first.\n\n**Response playbook.** Positive: thank personally, mention specifics, invite back. Negative: respond quickly (24–48h), empathize publicly, take resolution offline, follow up publicly when resolved. Never argue, never be defensive, never fake.\n\n**Platform strategy.** Prioritize where your customers look: Google (local SEO + trust), industry-specific (e.g., G2\u002FCapterra for software, TripAdvisor for hospitality), then secondary. Claim and complete every profile — unclaimed profiles collect unanswered complaints.\n\n**Reputation monitoring.** Alerts for new reviews and mentions, sentiment tracking over time, competitor review benchmarking. Speed matters — a negative review unanswered for weeks signals indifference.\n\n**Reviews as assets.** Showcase top reviews on site\u002Fsocial\u002Fads (with permission where needed), mine reviews for messaging (customer language is copy gold), and feed recurring complaints to product\u002Fops as improvement priorities.\n\n\n**The review request moment.** Ask when satisfaction peaks: after delivery confirmation, after a resolved support ticket, after a milestone achieved in-product. Never ask after a complaint or a failed interaction. In-product prompts at the moment of delight convert 5–10x better than post-purchase emails.\n\n**Responding to negatives (the HEARD method):** Hear them out (acknowledge specifically) → Empathize (genuine, not scripted) → Apologize where warranted → Resolve (offer a path forward) → Diagnose (fix the root cause). A thoughtful response to a 1-star review influences every future reader more than the review itself.\n\n**Platform strategy.** Google (dominant for local), Yelp (influential, filtered aggressively), Facebook (social proof), industry-specific (TripAdvisor, Healthgrades, G2).\nPrioritize by where your customers actually decide — not all platforms matter equally per vertical.\nClaim and complete profiles everywhere relevant; optimize effort toward the top 2–3.\n**Review velocity.** Steady streams beat bursts: 5–10 new reviews monthly per location sustains rankings and trust.\nSystematize asks (post-transaction triggers) rather than campaigning sporadically.\nMonitor velocity per location; stalled locations need intervention.\n**Sentiment analysis.** Categorize feedback themes (service, product, price, staff) → track trends → route insights to operations.\nReviews are free market research — aggregate them into operational improvements.\nShare positive themes with teams; recognition reinforces what works.\n## Practical workflow\n\n1. **Audit.** Current ratings per platform, review velocity, response rate and time, sentiment themes, competitor comparison. Find the gaps.\n2. **Claim and optimize profiles.** Every relevant platform: complete info, photos, accurate hours\u002Fservices, correct categories. Unclaimed profiles are reputation liabilities.\n3. **Build generation systems.** Post-transaction email\u002FSMS sequences (ask happy customers at the right moment), in-store QR codes, staff training (ask in person — highest conversion), and review links in receipts\u002Ffollow-ups. Target steady velocity, not bursts.\n4. **Respond systematically.** Daily monitoring, response SLA (24–48h), templates as starting points (personalize every response), escalation path for serious complaints, and a process for flagging fake\u002Fdefamatory reviews.\n5. **Showcase and leverage.** Review widgets on site, top reviews in ads and social, case studies from detailed reviews, and \"you asked, we fixed\" posts when reviews drive improvements.\n6. **Analyze and improve.** Monthly: rating trends, sentiment themes, response metrics, competitor movement. Quarterly: feed top complaint themes to operations with data.\n\n**Negative review response template:** acknowledge specifically → empathize genuinely → take it offline (name + direct contact) → resolve → follow up publicly. \"We're sorry to hear about [specific issue]. This isn't the experience we want. I'm [name], [title] — please reach me at [contact] so I can make this right.\"\n\n\n**Review generation system:** map the customer journey → identify 2–3 peak-satisfaction moments → build asks into those moments (in-product, email, SMS) → make leaving a review frictionless (direct links, no account creation) → thank reviewers personally → showcase reviews in marketing. Measure: review velocity, average rating trend, response rate, and response time.\n\n**Crisis protocol:** negative review velocity spike → assess validity (real issue or attack?) → respond publicly with HEARD → fix root cause → follow up privately → if fake\u002Fcoordinated, report with evidence. Never offer incentives for removing negative reviews — it violates most platforms' policies.\n\n**Multi-location program:** centralized platform (monitoring, response templates, analytics) → location-level ownership (managers respond within 24h) → escalation paths (serious complaints to senior staff) → monthly scorecards per location.\nBalance central efficiency with local authenticity — templated responses to everything feel robotic.\n**Viral incident response:** assess scope and validity → respond publicly (acknowledge, empathize, commit to action) → take detailed discussion private → implement fixes → follow up publicly with resolution.\nSpeed matters, but accuracy matters more — verify facts before responding publicly.\n## Common pitfalls\n\n- **Never asking.** Relying on organic reviews guarantees negativity bias. Ask systematically.\n- **Fake or incentivized positives.** Platform penalties, legal risk, and destroyed trust when exposed. Earn reviews honestly.\n- **Arguing with reviewers.** Public defensiveness amplifies damage. Empathize and move offline.\n- **Ignoring reviews.** Unanswered reviews — especially negative — signal you don't care. Respond to all negative, many positive.\n- **Review gating.** Only soliciting from happy customers (against most platforms' policies). Ask everyone; fix what you learn.\n- **Burst campaigns.** 50 reviews in a week then silence looks manipulated. Steady velocity wins.\n- **Not acting on feedback.** Reviews revealing the same complaint for months with no fix. Close the loop operationally.\n- **Incentivizing only positive reviews.** Asking only happy customers skews ratings and violates FTC\u002Fplatform rules. Ask everyone; earn the positives.\n- **Ignoring reviews.** Unanswered negatives signal indifference. Respond to 100% of negatives and a sample of positives.\n- **Fighting fake reviews emotionally.** Public accusations backfire. Report through proper channels with documentation; respond professionally regardless.\n- **Fake review panic.** Obsessing over competitors' suspicious reviews. Report with evidence, then focus on earning genuine reviews — authenticity wins long-term.\n- **Ignoring positive reviews.** Only responding to negatives. Thanking positive reviewers builds loyalty and encourages more reviews.\n","## Overview\n\nReviews are modern word-of-mouth: they drive local SEO, purchase decisions, and trust. This skill covers the full review practice — generating authentic reviews at scale, responding to positive and negative reviews, monitoring reputation across platforms, and using review insights to improve the business.\n\n\nReviews are the new word-of-mouth at scale: 90%+ of buyers read them, and star ratings directly move conversion. Review management is both defensive (responding to negatives, catching fake reviews) and offensive (generating authentic positives systematically). It is a compounding asset — every review works for you indefinitely.\n## When to use\n\n- Increasing review volume and ratings\n- Responding to negative reviews\n- Building a review generation system\n- Monitoring brand reputation\n- Improving local search via reviews\n- Turning reviews into marketing assets\n\n- Recovering from a negative review crisis\n- Building review generation into the customer journey\n- Monitoring brand sentiment across platforms\n- Managing reviews across 100+ locations\n- Responding to viral negative incidents\n- Building review programs for B2B services\n## Core concepts\n\n**The review funnel.** Ask → make it easy → follow up → respond → showcase. Most happy customers never review unless asked; most unhappy ones review unprompted. Systematic asking corrects the negativity bias.\n\n**Asking well.** Timing (right after positive moments: delivery, successful support, 5-star NPS), channel (email, SMS, in-app, in-person with QR codes), and simplicity (direct links to the right platform, no multi-step processes). Never incentivize with payments for positive reviews — it's against most platforms' policies and often illegal; you can incentivize honest reviews in some contexts, but check platform rules first.\n\n**Response playbook.** Positive: thank personally, mention specifics, invite back. Negative: respond quickly (24–48h), empathize publicly, take resolution offline, follow up publicly when resolved. Never argue, never be defensive, never fake.\n\n**Platform strategy.** Prioritize where your customers look: Google (local SEO + trust), industry-specific (e.g., G2\u002FCapterra for software, TripAdvisor for hospitality), then secondary. Claim and complete every profile — unclaimed profiles collect unanswered complaints.\n\n**Reputation monitoring.** Alerts for new reviews and mentions, sentiment tracking over time, competitor review benchmarking. Speed matters — a negative review unanswered for weeks signals indifference.\n\n**Reviews as assets.** Showcase top reviews on site\u002Fsocial\u002Fads (with permission where needed), mine reviews for messaging (customer language is copy gold), and feed recurring complaints to product\u002Fops as improvement priorities.\n\n\n**The review request moment.** Ask when satisfaction peaks: after delivery confirmation, after a resolved support ticket, after a milestone achieved in-product. Never ask after a complaint or a failed interaction. In-product prompts at the moment of delight convert 5–10x better than post-purchase emails.\n\n**Responding to negatives (the HEARD method):** Hear them out (acknowledge specifically) → Empathize (genuine, not scripted) → Apologize where warranted → Resolve (offer a path forward) → Diagnose (fix the root cause). A thoughtful response to a 1-star review influences every future reader more than the review itself.\n\n**Platform strategy.** Google (dominant for local), Yelp (influential, filtered aggressively), Facebook (social proof), industry-specific (TripAdvisor, Healthgrades, G2).\nPrioritize by where your customers actually decide — not all platforms matter equally per vertical.\nClaim and complete profiles everywhere relevant; optimize effort toward the top 2–3.\n**Review velocity.** Steady streams beat bursts: 5–10 new reviews monthly per location sustains rankings and trust.\nSystematize asks (post-transaction triggers) rather than campaigning sporadically.\nMonitor velocity per location; stalled locations need intervention.\n**Sentiment analysis.** Categorize feedback themes (service, product, price, staff) → track trends → route insights to operations.\nReviews are free market research — aggregate them into operational improvements.\nShare positive themes with teams; recognition reinforces what works.\n## Practical workflow\n\n1. **Audit.** Current ratings per platform, review velocity, response rate and time, sentiment themes, competitor comparison. Find the gaps.\n2. **Claim and optimize profiles.** Every relevant platform: complete info, photos, accurate hours\u002Fservices, correct categories. Unclaimed profiles are reputation liabilities.\n3. **Build generation systems.** Post-transaction email\u002FSMS sequences (ask happy customers at the right moment), in-store QR codes, staff training (ask in person — highest conversion), and review links in receipts\u002Ffollow-ups. Target steady velocity, not bursts.\n4. **Respond systematically.** Daily monitoring, response SLA (24–48h), templates as starting points (personalize every response), escalation path for serious complaints, and a process for flagging fake\u002Fdefamatory reviews.\n5. **Showcase and leverage.** Review widgets on site, top reviews in ads and social, case studies from detailed reviews, and \"you asked, we fixed\" posts when reviews drive improvements.\n6. **Analyze and improve.** Monthly: rating trends, sentiment themes, response metrics, competitor movement. Quarterly: feed top complaint themes to operations with data.\n\n**Negative review response template:** acknowledge specifically → empathize genuinely → take it offline (name + direct contact) → resolve → follow up publicly. \"We're sorry to hear about [specific issue]. This isn't the experience we want. I'm [name], [title] — please reach me at [contact] so I can make this right.\"\n\n\n**Review generation system:** map the customer journey → identify 2–3 peak-satisfaction moments → build asks into those moments (in-product, email, SMS) → make leaving a review frictionless (direct links, no account creation) → thank reviewers personally → showcase reviews in marketing. Measure: review velocity, average rating trend, response rate, and response time.\n\n**Crisis protocol:** negative review velocity spike → assess validity (real issue or attack?) → respond publicly with HEARD → fix root cause → follow up privately → if fake\u002Fcoordinated, report with evidence. Never offer incentives for removing negative reviews — it violates most platforms' policies.\n\n**Multi-location program:** centralized platform (monitoring, response templates, analytics) → location-level ownership (managers respond within 24h) → escalation paths (serious complaints to senior staff) → monthly scorecards per location.\nBalance central efficiency with local authenticity — templated responses to everything feel robotic.\n**Viral incident response:** assess scope and validity → respond publicly (acknowledge, empathize, commit to action) → take detailed discussion private → implement fixes → follow up publicly with resolution.\nSpeed matters, but accuracy matters more — verify facts before responding publicly.\n## Common pitfalls\n\n- **Never asking.** Relying on organic reviews guarantees negativity bias. Ask systematically.\n- **Fake or incentivized positives.** Platform penalties, legal risk, and destroyed trust when exposed. Earn reviews honestly.\n- **Arguing with reviewers.** Public defensiveness amplifies damage. Empathize and move offline.\n- **Ignoring reviews.** Unanswered reviews — especially negative — signal you don't care. Respond to all negative, many positive.\n- **Review gating.** Only soliciting from happy customers (against most platforms' policies). Ask everyone; fix what you learn.\n- **Burst campaigns.** 50 reviews in a week then silence looks manipulated. Steady velocity wins.\n- **Not acting on feedback.** Reviews revealing the same complaint for months with no fix. Close the loop operationally.\n- **Incentivizing only positive reviews.** Asking only happy customers skews ratings and violates FTC\u002Fplatform rules. Ask everyone; earn the positives.\n- **Ignoring reviews.** Unanswered negatives signal indifference. Respond to 100% of negatives and a sample of positives.\n- **Fighting fake reviews emotionally.** Public accusations backfire. Report through proper channels with documentation; respond professionally regardless.\n- **Fake review panic.** Obsessing over competitors' suspicious reviews. Report with evidence, then focus on earning genuine reviews — authenticity wins long-term.\n- **Ignoring positive reviews.** Only responding to negatives. Thanking positive reviewers builds loyalty and encourages more reviews.\n",{"name":5,"category":24,"description":7},"business-marketing","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-review-manager",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill review-manager",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill review-manager",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill review-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-review-manager\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]