Gridly

View saved version →

---
name: agency-report
description: Report across several client stores at once. Use when an agency or owner with more than one connected store asks for month-end numbers, a one-table comparison of stores, or a client report.
---

1. Call `list_stores` to see which stores are connected.
2. Call `multi_store_report` with the period (for example `last_month`). It returns one row per store: net revenue, orders, average order, refunds and top product.
3. Present one table. Never add numbers from stores that use different currencies.
4. If a store could not be read, say which one and why (the message tells you), and offer to retry.
5. For any store the owner wants to dig into, call the other tools with that store's address in the `store` argument.

View saved version →

---
name: campaign-planner
description: Plan discounts and promotions for a WooCommerce store from real sales and stock data. Use when the owner asks what promotion to run, how to clear slow stock, win back customers, or grow order size.
---

1. Call `suggest_campaigns`. Each idea includes the reason and ready-to-use settings for `create_coupon` or `update_products`.
2. Optionally call `customer_segments` (for example `segment: "lapsed"`) to size a win-back idea. Never reveal customers' emails; Gridly does not return them.
3. Explain two or three ideas in plain language with the reason from the data, then ask which one to set up.
4. Set it up with the normal two-step flow (preview, owner approves, then confirm). Offer `apply_at` if the owner wants it to start on a date.
5. Gridly does not send marketing emails. If a win-back idea needs emailing customers, say the owner should do that from their own email tool.

View saved version →

---
name: monday-check
description: Weekly shop check-in for a WooCommerce store. Use when the owner asks how the shop did, how last week or this month went, whether anything needs attention, or wants a quick status report.
---

Give the owner a calm, short weekly check using the Gridly tools. Do not dump raw data.

1. Call `compare_periods` with `period_a` = `last_week` (it compares with the week before by default). If the owner named another period, use that.
2. Call `top_products` for the same period with `limit` 3.
3. Call `store_health_check` and `low_stock_report`.
4. Reply in this shape:
   - **One sentence** on how the week went (revenue and orders, with the % change).
   - **Top 3 products**, one line each.
   - **Needs attention:** only items with a count above zero (out of stock, stuck orders, missing prices). Skip anything fine.
   - **One suggested next step**, phrased as a question the owner can say yes to (for example, "Want me to preview a restock list?").
5. If a tool says the Free plan covers only 30 days, mention it once, in one factual line, and move on.

If the owner has several stores, ask which one, or use `multi_store_report` for a one-table summary.

View saved version →

---
name: order-help
description: Look up and update WooCommerce orders. Use when the owner asks where an order is, wants order details, a customer's orders, unpaid or stuck orders, or wants to mark an order completed or add a note.
---

- To find orders, use `find_orders` (filters: status, period, `older_than_days`, amount, customer email, product). Names in lists are shortened on purpose.
- For one order, use `get_order` with the order number. Share only what the owner asked for; do not repeat full addresses or emails unless needed.
- To change status or add a note, use `update_order`: preview first, show the owner, and call again with `confirm: true` and the `preview_id` only after a clear yes.
- A note to the customer is emailed by WooCommerce. Always ask whether a note should be private or visible to the customer.
- Marking an order completed also emails the customer. Say so in the preview.
- Refunds are not possible here. Tell the owner to use WooCommerce's refund button.

View saved version →

---
name: product-descriptions
description: Write or rewrite WooCommerce product names, descriptions, short descriptions and SEO titles. Use when the owner asks to improve, refresh, shorten or write product text, or to fix thin descriptions.
---

1. Call `get_brand_voice`. If the owner has a saved style, follow it. If they have none, ask one question about tone and length, then offer to save it with `save_brand_voice`.
2. Find the products: `find_products` with `max_description_words` (for example 50) or `missing: ["description"]`, or the specific products the owner named.
3. Draft the new text yourself. Keep facts to what is already in the store (name, category, existing description). Do not invent specifications, materials, certifications or claims.
4. Call `apply_product_content` WITHOUT `confirm` to preview before/after for each product. Optionally include `meta_title` (about 60 characters) and `meta_description` (about 150 characters).
5. Show the owner the previews and wait for approval. Only then call it again with `confirm: true` and the `preview_id`.
6. Mention the change number and that "undo change N" restores the old text.

View saved version →

---
name: safe-bulk-edit
description: Make changes to many products, prices, stock levels, categories or coupons in a WooCommerce store safely. Use whenever the owner asks to raise or lower prices, change stock or status, tag or categorise products, create a discount code, or undo or schedule such a change.
---

Every Gridly change tool works in two steps. Never skip the first.

1. **Preview.** Call the tool (`update_products`, `create_coupon`, `update_order`, `apply_product_content`) WITHOUT `confirm`. Nothing changes yet. You get a `preview_id`.
2. **Show it.** Show the owner the preview plainly: how many items, the old and new values for the first few, and anything skipped. If the filter looks too broad (for example it includes products the owner did not mean), say so and offer to narrow it.
3. **Ask for a clear yes.** Only after the owner explicitly approves, call the same tool again with `confirm: true` and the `preview_id`.
4. **Report.** Say what was done and give the change number. Tell the owner they can say "undo change N".

Rules:
- Never invent a `preview_id`. Previews expire after 15 minutes; if one expired, run the preview again.
- To apply later instead of now, add `apply_at` (the store's local time, `YYYY-MM-DDTHH:MM`) to the confirm call. Use `list_scheduled_changes` and `cancel_scheduled_change` to manage them.
- To reverse a change, call `undo_change` with the change number and follow the same preview-then-confirm steps. Use `change_history` to find numbers.
- Refunds and payments cannot be made with Gridly. If asked, say so and point to WooCommerce itself.