{"id":87212,"plugin_id":"plugin_asdk_app_6ac7858900fc81919c8aa4b677d8a058","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-09T12:07:54.119Z","digest":"4f1f851fba605c3b485dd34805283fc8d7c996b28f4e76434c67f951cc684582","against":null,"payload":{"description":"Summarize recurring themes in sampled public Google Maps, Yelp, Amazon or Walmart reviews with HasData. Use for business or product review comparisons, not posting, removing or verifying reviewers.","included_files":[],"name":"review-insights","skill_md_contents":"---\nname: review-insights\ndescription: Summarize recurring themes in sampled public Google Maps, Yelp, Amazon or Walmart reviews with HasData. Use for business or product review comparisons, not posting, removing or verifying reviewers.\n---\n\n# Summarize customer review evidence\n\nRead `../hasdata-research/SKILL.md` and `../hasdata-research/references/tool-contract.md` before tool calls. Their scope, security and credit limits apply.\n\nHonor the requested review source. For Maps, reuse a known placeId or search by business name and city. For Yelp, resolve the directory's own placeId. For Amazon or Walmart, use a returned product identifier or an unambiguous supplied product URL. Read the relevant section of `../hasdata-research/references/tool-catalog.md`. Never reuse IDs between platforms. Ask when several branches or product variants are plausible rather than charging for a guessed target.\n\nFetch one page. For recent Maps feedback use sortBy:newestFirst unless another order was requested. Other platforms have different sort enums, filters and pagination fields. Use the chosen tool's actual schema and do not pass Maps options to a product or Yelp review tool. Do not invent topic or aspect IDs. Further pages use the source's supported page field or returned token within an agreed budget.\n\nRead actual review fields from the payload. Separate review text, star rating, returned publication date and available source URL. State the number of reviews with readable text, the returned sample size and sort order. Relative dates are approximate. Do not claim a calendar cutoff was enforced unless the tool supports it and the returned dates justify it.\n\nGroup recurring themes with supporting examples. Count each review once per theme. Give concise faithful quotes and available review links; if individual URLs are absent, link the place or returned snapshot and say individual links were not returned. Do not copy unnecessary reviewer profile details. Distinguish recurring issues from an isolated complaint, and evidence from your interpretation.\n\nReturn a short findings summary with theme counts and practical follow-up suggestions. Label the suggestions as analysis, not claims from the reviews. Do not infer motivations or sensitive traits, exaggerate the prevalence of an issue, or turn a sampled sentiment count into the business's overall customer satisfaction rate. A business rating is not an average you calculated from this sample.\n\nFor comparing two businesses, use the same sort order and a bounded page count for each. Flag differing sample sizes and missing text. Without earlier saved review observations, do not claim that sentiment improved or deteriorated.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}