Update to Brainerce

{
  "name": "brainerce-product-onboarding",
  "description": "Add a product to a Brainerce store properly, from creating it through to category, tags, stock and publishing. Use when the merchant says add a product, I have something new to sell, list this item, put this in the shop, set up my new range, copy an existing product, or fix the stock count on something. Also covers duplicating a near-identical product and correcting inventory after a stock take. For store owners, not developers. Do not choose this to change price or description on a product that already exists and is set up, that is a quick edit and needs no sequence. Do not choose this for reading reviews or ratings, use brainerce-analytics. Do not choose this to find products that were left as drafts, use brainerce-store-health. Do not choose this to decide variant versus custom field, use brainerce-store-architecture. Keywords: add product, new product, list an item, create product, upload product, stock count, inventory, restock, categorise, tags, publish, duplicate product, product variants.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 1102
    },
    {
      "relative_path": "assets/icon.png",
      "size_in_bytes": 3208
    }
  ],
  "skill_md_contents": "---\nname: brainerce-product-onboarding\ndescription: \"Add a product to a Brainerce store properly, from creating it through to category, tags, stock and publishing. Use when the merchant says add a product, I have something new to sell, list this item, put this in the shop, set up my new range, copy an existing product, or fix the stock count on something. Also covers duplicating a near-identical product and correcting inventory after a stock take. For store owners, not developers. Do not choose this to change price or description on a product that already exists and is set up, that is a quick edit and needs no sequence. Do not choose this for reading reviews or ratings, use brainerce-analytics. Do not choose this to find products that were left as drafts, use brainerce-store-health. Do not choose this to decide variant versus custom field, use brainerce-store-architecture. Keywords: add product, new product, list an item, create product, upload product, stock count, inventory, restock, categorise, tags, publish, duplicate product, product variants.\"\ncompatibility: ChatGPT, Claude Code, Claude Desktop, Cursor\nmaintainer: Brainerce\nmetadata:\n  author: Brainerce\n  version: \"1.0.0\"\n---\n\nGet a new product from \"I have this thing to sell\" to a listing customers can actually find and buy.\n\n## Core principle\n\nA created product is not a finished product. A merchant who is told \"done\" and then finds the item invisible on their own storefront, uncategorised, or with no stock, has been misled. Walk the whole sequence, and say which parts you skipped.\n\n## When to use this skill first\n\n- \"Add a product\", \"I have something new to sell\", \"list this\".\n- \"Set up my new range\" or several products at once.\n- \"Make another one like this\": duplicating an existing listing.\n- \"Fix the stock on X\", \"I counted 40 of these\".\n\n## When NOT to use this skill first\n\n- Changing a price or a description on an existing, fully set up product: just do it, no sequence needed.\n- \"What do people think of this product\", ratings and reviews: use `brainerce-analytics`.\n- \"Find products I left as drafts\": use `brainerce-store-health`.\n- \"Put this product on sale\": use `brainerce-launch-a-sale`.\n- \"Should size be a variant or an option\", or any question about how the catalog should be modelled before the product exists: use `brainerce-store-architecture`.\n\n---\n\n## The sequence\n\nDo these in order. Later steps depend on earlier ones, and skipping one is how products end up invisible.\n\n### 1. Look before you create\n\nCall `list_products` with the name the merchant gave. If something close already exists, say so and ask whether they want a new product or an edit to that one. Creating a near-duplicate is easy to do and annoying to undo, and this connector cannot delete the mistake.\n\nIf the merchant wants something very like an existing product, `duplicate_product` is faster and less error prone than retyping everything. Duplicate first, then edit the differences with `update_product`.\n\n### 2. Create it\n\nCall `create_product`. Ask for what is missing rather than filling it in yourself:\n\n- **Name** and **price**, always. Read the currency from `get_store`; do not assume.\n- **Description**: offer to draft one, but show it to the merchant before it goes live. This is their voice, on their storefront.\n- **Images**: if the merchant has image URLs, pass them; the platform downloads and stores the images rather than linking to someone else's server.\n- **Variants**: sizes, colours, materials. Ask if the product obviously has them (\"a t-shirt\" almost certainly does) and do not silently create a single-variant product for something that needs five.\n\n### 3. Put it somewhere customers will find it\n\nCall `list_categories`, then place the product in a real category. If nothing fits, `create_category` makes one, but check the list first; stores accumulate near-duplicate categories fast.\n\n### 4. Tag it\n\nCall `list_tags` before `create_tag`. Reuse an existing tag over creating \"Summer\" next to \"summer\" and \"Summer 2026\". Tags are how the merchant will filter and how sales get targeted later.\n\n### 5. Set stock\n\nCall `set_product_stock`. A product with no stock is not buyable, and a merchant who thinks they have listed something for sale will not check. If the merchant has not said how many, ask; do not default to a number.\n\n`get_product_inventory` reads back what is actually there, and is the tool for a stock take correction as well.\n\n### 6. Offer to publish, do not assume\n\nProducts can exist as drafts. Tell the merchant which state it is in and ask before making it visible. \"Do you want this live on the storefront now, or held as a draft while you add photos?\" is one sentence and prevents both of the bad outcomes.\n\n## Response shape\n\n> ✓ Ceramic Mug is created at 65 ILS, in Kitchen, tagged handmade and gift, with 40 in stock.\n>\n> It is currently a draft, so customers cannot see it yet.\n>\n> Want me to publish it, or would you rather add photos first?\n\n**Partly done, use this shape:**\n\n> ✓ Ceramic Mug is created at 65 ILS with 40 in stock.\n>\n> Two things I did not do: it is not in a category yet, and it has no images. Uncategorised products are hard for customers to find.\n>\n> Want me to put it in Kitchen?\n\n## Rules\n\n- Never say \"added to your store\" for a draft. Say it is a draft and what that means.\n- Check `list_products` before creating, and `list_tags` and `list_categories` before creating those. Duplicates cannot be deleted from here.\n- Ask for stock rather than defaulting to zero or to some number you picked.\n- Show generated descriptions to the merchant before publishing. This is their shop's voice.\n- `create_product` reaches an external origin when it downloads images from URLs, and running it twice creates two products, not one. If a call is ambiguous about whether it went through, check with `list_products` rather than re-running it.\n- `update_product` replaces the fields it touches rather than merging into them. Read the current product with `get_product` before an edit so you know what you are about to overwrite.\n- Several products at once: do them one at a time and report as you go. This connector has no bulk create, and a half-finished batch is worse than a slow one.\n- This connector cannot delete a product. Say so if the merchant asks, and point at the Brainerce dashboard.\n\n## Cross-skill connections\n\n- Putting the new product on sale: `brainerce-launch-a-sale`.\n- Reviews and ratings on it: `brainerce-analytics`.\n- Finding old drafts and out-of-stock items across the store: `brainerce-store-health`.\n- Deciding variant versus custom field, or category versus tag: `brainerce-store-architecture`.\n- Filling in a custom field on the new product: `brainerce-custom-fields`.\n\nRoute once, and do not bounce back and forth.\n"
}