{"id":30787,"plugin_id":"plugin_asdk_app_6ab6a9e74b3881918424f863df9a6cdb","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-09T18:02:51.852Z","digest":"c906545b97aa66e8841a19d9b5eaca5ab7f351cac87dd68b085dfcaa932d0641","against":null,"payload":{"description":"Give a Capi merchant a short daily briefing on their store — sales against the previous period, what needs attention, stock at risk and customer service — when they ask how the store is doing, for a summary, a morning briefing, or \"what should I do today\".","included_files":[],"name":"store-daily-briefing","skill_md_contents":"---\nname: store-daily-briefing\ndescription: Give a Capi merchant a short daily briefing on their store — sales against the previous period, what needs attention, stock at risk and customer service — when they ask how the store is doing, for a summary, a morning briefing, or \"what should I do today\".\n---\n\nUse this skill when a merchant asks for an overview of their store: \"how is my store doing\", \"give me a summary\", \"morning briefing\", \"what should I focus on today\", or the same in Arabic (\"شلون المتجر\", \"ملخص اليوم\", \"شو لازم أعمل اليوم\").\n\n1. Call `sales_report` with `period: \"today\"`. If the merchant names a period (\"this week\", \"last month\"), use the closest of `yesterday`, `last_7_days`, `last_30_days` or `last_90_days` instead.\n2. Call `store_problems` once.\n3. Call `service_report` with the same period as step 1.\n4. Only if `sales_report` or `store_problems` mentions low or zero stock, call `find_my_products` with `filter: \"out_of_stock\"`.\n\nThen answer in the merchant's language, in this order and briefly:\n\n- **Sales** — revenue, orders and average order value against the previous period, with the change. Say plainly when a figure went down.\n- **Needs attention** — at most five items from `store_problems`, most urgent first, each with its dashboard link.\n- **Stock** — out-of-stock best sellers by name, if any.\n- **Customer service** — the rating and the one main reason behind low ratings, if the report gives one.\n- **Next step** — one concrete action the merchant can take today.\n\nRules:\n\n- Use only figures the tools returned. If a tool returns an error or no data, say so for that section; never estimate or fill a gap.\n- Do not call any tool that changes settings (knowledge base, rules, working hours, agent behaviour, versions) during a briefing. Offer the change and wait for the merchant to ask for it.\n- Never ask for, or try to reveal, customer names, phone numbers, emails or addresses. The tools do not return them.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}