{"id":50089,"plugin_id":"plugin_asdk_app_6abed6b6b0e8819181fc9acc6a2944c7","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:42:03.089Z","digest":"bf2cfb2e79a6b21b8ffa34cea18d806128bf40d90622b9cab604a37c295641c3","against":null,"payload":{"description":"Write or revise customer review request copy for email, SMS, receipts, or signage, using a supplied business identity and review destination. Use for neutral requests for genuine customer feedback.","included_files":[],"name":"write-review-requests","skill_md_contents":"---\nname: write-review-requests\ndescription: Write or revise customer review request copy for email, SMS, receipts, or signage, using a supplied business identity and review destination. Use for neutral requests for genuine customer feedback.\n---\n\nDraft review requests suited to the user's channel, business voice, and customer context. Respect requested language and length. This workflow drafts copy; it has no customer list or sending service. If the user also wants a review link or QR code, use the packaged [review-link workflow](../create-review-link/SKILL.md) when its tools are available.\n\n- Ask customers for an honest account of their experience. Avoid asking only happy customers, making a public-review link conditional on positive feedback, or offering rewards for reviews.\n- Use the supplied destination exactly. If missing, use a clearly marked [review link] placeholder and explain that the owner must replace it before sending. Never fabricate a business's Google review URL.\n- Personalize using supplied facts. Do not invent a recent visit, purchase, consent, customer relationship, incentive, or already-sent message.\n- Keep private support available without using it to divert unhappy customers from the same review opportunity offered to everyone else.\n- If the user requests an incentive or selective solicitation, provide a neutral version and briefly explain the change. Do not present this workflow as a legal compliance certification.\n\nProvide ready-to-edit copy and identify any remaining placeholders. For email, include a subject and body; for SMS, keep the request concise. Sending schedules and campaign variants are optional and should follow the user's scope. Never claim a message has been sent.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}