← BrainerceCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Brainerce
Snapshot Sep 30, 2026 · 23:07 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Set up a sale, promotion or discount on a Brainerce store and confirm it is actually live. Use when the merchant says take 20% off, run a sale, put the winter range on sale, launch a promotion, create a discount code, set up a voucher, offer free shipping over a threshold, or schedule a Black Friday or holiday deal. The core of this skill is the choice between an automatic discount that applies by itself in the cart and a coupon code the shopper has to type, because getting that wrong is the mistake merchants notice. For store owners, not developers. Do not choose this to review how a past promotion performed, use brainerce-analytics. Do not choose this to hunt for expired or forgotten promotions across the store, use brainerce-store-health. Keywords: sale, discount, promotion, promo code, coupon, voucher, percent off, money off, BOGO, buy one get one, free shipping, bundle, Black Friday, clearance, markdown.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 1086
},
{
"relative_path": "assets/icon.png",
"size_in_bytes": 3208
}
],
"name": "brainerce-launch-a-sale",
"skill_md_contents": "---\nname: brainerce-launch-a-sale\ndescription: \"Set up a sale, promotion or discount on a Brainerce store and confirm it is actually live. Use when the merchant says take 20% off, run a sale, put the winter range on sale, launch a promotion, create a discount code, set up a voucher, offer free shipping over a threshold, or schedule a Black Friday or holiday deal. The core of this skill is the choice between an automatic discount that applies by itself in the cart and a coupon code the shopper has to type, because getting that wrong is the mistake merchants notice. For store owners, not developers. Do not choose this to review how a past promotion performed, use brainerce-analytics. Do not choose this to hunt for expired or forgotten promotions across the store, use brainerce-store-health. Keywords: sale, discount, promotion, promo code, coupon, voucher, percent off, money off, BOGO, buy one get one, free shipping, bundle, Black Friday, clearance, markdown.\"\ncompatibility: ChatGPT, Claude Code, Claude Desktop, Cursor\nmaintainer: Brainerce\nmetadata:\n author: Brainerce\n version: \"1.0.0\"\n---\n\nTake a merchant from \"put this on sale\" to a promotion that is live, correct, and described back to them accurately.\n\n## Core principle\n\nYou are helping someone run their shop. They do not think in entity names, rule types or ISO timestamps, so do not make them. Ask about the sale in the words they used, then translate. Never report a promotion as created until a listing tool has shown it back to you.\n\n## When to use this skill first\n\n- The merchant wants money taken off something: a product, a category, an order total, or shipping.\n- The merchant asks for a discount code to hand out.\n- The merchant wants a promotion scheduled for a date range or a named shopping event.\n- The merchant asks whether a sale they set up is running.\n\n## When NOT to use this skill first\n\n- \"How much did the sale make\", \"did the promotion work\", \"what is my revenue this week\": use `brainerce-analytics`.\n- \"Find promotions I forgot to turn off\", \"audit the store\": use `brainerce-store-health`.\n- \"The order should have had the discount on it\": that is an order question, use `brainerce-order-handling`.\n\n---\n\n## Step 1: automatic discount, or a code? Decide this before anything else\n\nTwo different things are called a discount, and they behave differently for the shopper.\n\n| | Automatic discount | Coupon |\n|---|---|---|\n| Tool | `create_discount_rule` | `create_coupon` |\n| Shopper experience | Price drops by itself in the cart | Shopper must type a code at checkout |\n| Who gets it | Everyone the rule targets | Only people who have the code |\n| Merchant says | \"20% off all jackets\", \"sale next week\", \"free shipping over 200\" | \"a code for my newsletter\", \"SPRING20\", \"a voucher for this customer\" |\n\n**The default is the automatic discount.** When the merchant says \"give 10% off everything next week\" and never mentions a code, they mean the price drops on its own. Reach for `create_discount_rule`.\n\n**Use `create_coupon` only when** the merchant asks for a code, names a code word, or wants something they can hand to specific people.\n\n**When it genuinely could be either, ask one short question before creating anything:**\n\n> Quick check before I set this up: should the 20% come off by itself for everyone, or do you want a code that customers type in at checkout?\n\n⛔ Never create a coupon and then describe it as an automatic discount. A merchant who is told \"the discount is live\" and then sees full prices on their own storefront has been given a wrong answer, not an imprecise one.\n\n## Step 2: gather what the promotion needs\n\nAsk only for what is missing, and only what changes the result.\n\n- **What is on sale.** Everything, a category, specific products, or the order total. Use `list_products` or `list_categories` to resolve names the merchant used into real ones. If a name matches nothing, say so and offer the closest matches rather than picking one.\n- **How much.** A percentage or a fixed amount. Read the store's currency from `get_store` rather than assuming; do not say dollars to a merchant selling in shekels or euros.\n- **When.** A start and an end. \"Next week\" and \"for the weekend\" need turning into real dates, so state the dates you are using in your confirmation and let the merchant correct them.\n- **Limits, only if the merchant raises them.** Usage caps, per-customer caps, a budget ceiling, whether it can stack with other offers.\n\nDo not invent limits the merchant did not ask for, and do not ask about every optional field. A promotion with sensible defaults that they can adjust beats an interrogation.\n\n## Step 3: create it\n\n**Automatic discount:** call `create_discount_rule`. Pick the type from what the merchant described:\n\n- `PRODUCT_DISCOUNT`: money off specific products or a category.\n- `ORDER_DISCOUNT`: money off the order total.\n- `BUY_X_GET_Y` and `BUY_X_GET_X`: buy one get one, and its variants.\n- `VOLUME_DISCOUNT`: cheaper per unit at higher quantities.\n- `SHIPPING_DISCOUNT`: free or reduced shipping.\n- `BUNDLE`: a set of products priced together.\n\n**Coupon:** call `create_coupon` with the code the merchant chose. Codes are normalised to uppercase, so tell them the code as it will actually appear. If they want to know what the coupon would take off a real order before announcing it, `preview_coupon_for_order` computes it without applying anything.\n\n## Step 4: verify before you claim it worked\n\nCall `list_discount_rules` (or `list_coupons` for a code) and confirm the thing you just created is there with the status you expect. A creation call that returned without an error is not the same as a promotion the shopper will see.\n\nIf it is scheduled rather than active, say so plainly. Merchants read \"live\" as \"working right now\".\n\n## Step 5: tell the merchant, in their words\n\n**Automatic discount, use this shape:**\n\n> ✓ Your 20% off sale on Winter Jackets is set up and starts Monday 3 November, ending Sunday 9 November.\n>\n> Customers do not need a code. The lower price shows up on its own in the cart.\n>\n> Want me to turn it on now instead of Monday, or add anything else to it?\n\n**Coupon, use this shape:**\n\n> ✓ Your discount code SPRING20 is live now and runs until 31 March. It takes 20% off the order.\n>\n> Customers have to type SPRING20 at checkout for it to apply, so it only reaches the people you share it with.\n>\n> Want me to check what it would take off a typical order?\n\n**Could not do it, use this shape:**\n\n> I could not set that up: there is no category called \"Wintre Jackets\" in your store. The closest ones are Winter Jackets and Jackets. Which did you mean?\n\n## Rules\n\n- Verify with a listing tool before you say it is live. Every time.\n- Say \"code\" out loud whenever a coupon is involved, and say \"no code needed\" whenever it is a discount rule. The distinction is the whole point.\n- Use the store's real currency from `get_store`, and give dates as dates rather than \"next week\".\n- If the merchant asks for a discount on something that does not exist, name the closest real matches and stop. Do not put the sale on a product you guessed at.\n- Turning an existing promotion off is `toggle_discount_rule`, and it is worth offering when a merchant sounds worried about how much a sale is costing.\n- This connector cannot delete a coupon or a discount rule. If the merchant wants one gone rather than switched off, say that removal is done in the Brainerce dashboard.\n- Never describe stacking behaviour you did not set. If the merchant asks whether the new sale combines with an existing one, read the rules back with `list_discount_rules` rather than guessing.\n\n## Cross-skill connections\n\n- Performance of a promotion after the fact: `brainerce-analytics`.\n- Sweeping the store for expired or forgotten promotions: `brainerce-store-health`.\n- A specific order that should have been discounted: `brainerce-order-handling`.\n\nRoute once, and do not bounce back and forth.\n"
}SHA-256 of public snapshot: 73b7991af177d3b62e0482380052d6cf5f0fec090f7e68cadcee795811d95041