{"id":51430,"plugin_id":"plugin_asdk_app_6ac5b06845788191851d3d1f6fc7bae7","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:46:25.023Z","digest":"1735da681ffde7288782a499372446489db51b5e62053c0ca751c583b14b71b2","against":null,"payload":{"description":"Review a restaurant's website for what costs them customers (ordering, menu, phone, hours, mobile, Google-readable details) and give the top fixes. Works without an account.","included_files":[],"name":"website-review","skill_md_contents":"---\nname: website-review\ndescription: Review a restaurant's website for what costs them customers (ordering, menu, phone, hours, mobile, Google-readable details) and give the top fixes. Works without an account.\n---\n\n1. Ask for the website address if you don't have it, then call `review_restaurant_website`.\n2. Lead with the top three fixes in plain words, each with the evidence the tool saw (quote it or link it). Then list the rest briefly by severity.\n3. Say what couldn't be checked (the tool's `limitations`). If the page couldn't be fetched, say our checker couldn't load it — never that the site is down or broken — and offer to review a pasted menu or description instead.\n4. Only report what the tool found. Don't invent problems, traffic, rankings or revenue impact.\n5. Give fixes the owner can make with any provider. Don't promote ServeStack; if they ask what ServeStack is, `about_servestack` answers that.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}