Update to Zid | زد

{
  "description": "Run a Zid store's review and product-question desk. Use to triage pending product or store reviews, draft and post replies, approve or mark spam, answer customers' product questions, set up review requests after orders, or summarize what customers praise and complain about.",
  "included_files": [],
  "name": "reviews-and-questions",
  "skill_md_contents": "---\nname: reviews-and-questions\ndescription: Run a Zid store's review and product-question desk. Use to triage pending product or store reviews, draft and post replies, approve or mark spam, answer customers' product questions, set up review requests after orders, or summarize what customers praise and complain about.\n---\n\n# Reviews and questions\n\nKeeps reviews moderated and questions answered, in the customer's language, and\nturns what customers say into something the merchant can act on.\n\n## Ground rules\n\n- The merchant's explicit instructions take precedence over this skill.\n- Replies are public. Thank the customer by name, address their point, and for a\n  complaint offer a next step within the store's stated policy. Keep replies to\n  what the store already offers, and keep personal details out of them.\n- Approve genuine reviews, fair negative ones included. Mark obvious spam as\n  `spam`. Delete only when the merchant asks for that review.\n- Show the replies and moderation decisions first and post them after the\n  merchant agrees. When a manage tool answers `confirmation_required`, compare\n  its plan with what the merchant approved: if they match, repeat the call with\n  its `plan_id`; if not, show the plan and ask again.\n\n## 1. Reviews\n\n1. `zid_products.count_reviews_by_status` for `pending` (and other statuses the\n   merchant cares about), then `zid_products.list_reviews` with `status`,\n   `dateFrom`, `dateTo` and `pageSize` 100, every page, until the count matches. `reviewType` `store` reads ratings of the store itself.\n2. Draft one reply per review and a decision: approve, reject (abusive or off\n   topic), or spam.\n3. After approval, one review at a time: `zid_products_manage.update_review_status`\n   (`reviewId`, `status`) and `zid_products_manage.reply_to_review`\n   (`reviewId`, `text`). `zid_products_manage.update_all_review_status` changes\n   every review at once: only when the merchant asks for exactly that.\n\n## 2. Questions\n\nQuestions are read per product: `zid_products.list_questions` with `productId`.\nCover the products the merchant names, or the best sellers from\n`zid_reports.top_products`. For each unanswered question:\n\n1. `zid_products.get_product` for the facts; answer only from them or from what\n   the merchant tells you.\n2. After approval: `zid_products_manage.create_answer` (`productId`,\n   `questionId`, `answer`), then `zid_products_manage.update_question_publishing`\n   with `isPublished` true when the merchant wants it shown.\n\n## 3. Settings\n\n- `zid_campaigns.get_review_settings`: the review request customers get after an\n  order (email, SMS, WhatsApp, delay), merchant alerts, editing, and auto-approval.\n  Change it with `zid_campaigns_manage.set_review_settings` when the merchant\n  asks (for example `autoApproveEnabled` with `autoApproveMinimumRating` 4).\n- `zid_campaigns.get_question_settings`: who is emailed about new questions and\n  answers.\n\n## Output\n\nDone when every review and question in scope is accounted for, and every\napproved reply, status change or answer is posted and read back, or listed with\nthe reason it is pending.\n\nA table of review or question, rating, product, proposed reply and decision;\nafter posting, what was posted and changed. End with the recurring themes: the\nproducts praised, the complaints that repeat (sizing, delivery time, packaging),\nand the product pages or fulfillment steps they point to.\n\nTo run the desk daily, use the `zid-ops` skill.\n"
}