@wix/agent-skills 1.30.0 → 1.31.1

package/skills/wix-vibe-headless/platforms/base44-ecom-light-seed-with-install.md

@@ -112,7 +112,13 @@ fails. You can finish without waiting for those images or replacing their placeh
 
 **Never paste a Wix dashboard link or path.**
 
-**Before writing your final text response, make one handoff call** — `search_base44_docs(query="how do I manage my store's products, orders and inventory?", prefer_dashboard=true)`. Use its handoff guidance, note that the seeded catalog is mock data they can edit, replace or delete, and state any requested workflows that remain unfinished and what is needed to complete them.
+**Before writing your final text response, make one handoff call** — `search_base44_docs(query="how do I manage my store's products, orders, inventory and payments?", prefer_dashboard=true)`. Use its handoff guidance, note that the seeded catalog is mock data they can edit, replace or delete, and state any requested workflows that remain unfinished and what is needed to complete them.
+
+**A payment ask is a store ask.** The store carries its own checkout, in every region, so
+nothing separate connects payments and no payment provider is installed alongside it — send
+the user to the same dashboard page the handoff call names. A note that Base44 Payments /
+Wix Payments is unavailable in their region is about a provider installed into the app, and
+says nothing about their store's checkout.
 
 ## Additional Wix functionality
 

package/skills/wix-vibe-headless/platforms/base44-ecom-light-seed.md

@@ -106,7 +106,13 @@ fails. You can finish without waiting for those images or replacing their placeh
 
 **Never paste a Wix dashboard link or path.**
 
-**Before writing your final text response, make one handoff call** — `search_base44_docs(query="how do I manage my store's products, orders and inventory?", prefer_dashboard=true)`. Use its handoff guidance, note that the seeded catalog is mock data they can edit, replace or delete, and state any requested workflows that remain unfinished and what is needed to complete them.
+**Before writing your final text response, make one handoff call** — `search_base44_docs(query="how do I manage my store's products, orders, inventory and payments?", prefer_dashboard=true)`. Use its handoff guidance, note that the seeded catalog is mock data they can edit, replace or delete, and state any requested workflows that remain unfinished and what is needed to complete them.
+
+**A payment ask is a store ask.** The store carries its own checkout, in every region, so
+nothing separate connects payments and no payment provider is installed alongside it — send
+the user to the same dashboard page the handoff call names. A note that Base44 Payments /
+Wix Payments is unavailable in their region is about a provider installed into the app, and
+says nothing about their store's checkout.
 
 ## Additional Wix functionality
 

package/skills/wix-vibe-headless/platforms/base44-ecom-light.md

@@ -72,7 +72,13 @@ fails. You can finish without waiting for those images or replacing their placeh
 
 **Never paste a Wix dashboard link or path.**
 
-**Before writing your final text response, make one handoff call** — `search_base44_docs(query="how do I manage my store's products, orders and inventory?", prefer_dashboard=true)`. Use its handoff guidance, state any requested workflows that remain unfinished and what is needed to complete them.
+**Before writing your final text response, make one handoff call** — `search_base44_docs(query="how do I manage my store's products, orders, inventory and payments?", prefer_dashboard=true)`. Use its handoff guidance, state any requested workflows that remain unfinished and what is needed to complete them.
+
+**A payment ask is a store ask.** The store carries its own checkout, in every region, so
+nothing separate connects payments and no payment provider is installed alongside it — send
+the user to the same dashboard page the handoff call names. A note that Base44 Payments /
+Wix Payments is unavailable in their region is about a provider installed into the app, and
+says nothing about their store's checkout.
 
 ## Additional Wix functionality
 

package/skills/wix-headless-kit/guides/no-machine.md

@@ -1,115 +0,0 @@
-# No machine: the kit's run through the Wix APIs
-
-Read when you cannot run the commands this skill is built on: no shell, no file system, no Node, a
-sandbox that blocks the install, the CLI or the login, or a host that only talks to Wix through
-the Wix MCP. Nothing in this guide installs, downloads or runs anything. It walks the run of
-SKILL.md step by step and names, for each, the Wix API call the CLI or the script performs, and
-the file beside this skill that carries the contract.
-
-## Where these skills are
-
-This skill is one of a set, and the guide reads from three of them:
-
-- `<SKILL_ROOT>` — this skill, `wix-headless-kit`: the run, its guides, the Verticals table.
-- `<TEMPLATES>` — `wix-headless-templates`: the shipped, verified code per Wix Business Solution,
-  one folder each, with its `INSTRUCTIONS.md` (the contracts), `seed/` (the seed script and
-  `SEED.md`) and `rest/` (the data layer over plain `fetch`). Installed beside this skill, or
-  fetched to `<SKILL_ROOT>/templates/`.
-- `<MANAGE>` — `wix-manage`: REST recipes to configure and manage a site's business solutions, one
-  recipe per operation with the exact endpoint and payload; its `SKILL.md` is the index.
-- `<DOCS>` — `wix-docs`: how to look up the Wix API and SDK documentation and confirm a method's
-  exact shape before writing a call.
-
-They install together and sit beside each other. When you are reading this skill online rather
-than from an install, the others are published alongside it, by those names, and each skill's
-manifest lists its files. Read each file in full: a fetch tool that summarizes drops the exact
-calls and shapes; a tool that returns the file's text, or one that runs code and can fetch a URL,
-does not.
-
-Two things such a run does not produce, and never claims: a frontend built from the shipped `app/`
-code (that needs a build), and a release of one. Everything else the kit does to a site, it does
-through calls you can make.
-
-## 0. Identity
-
-Every call below runs as the site owner, with whatever identity your host gives you: the Wix
-MCP's `ExecuteWixAPI` carries the user's login; an API key from the user's account goes in the
-`Authorization` header of any call, as `<MANAGE>/SKILL.md` describes; a site token from the Wix CLI
-works the same way when the user runs the CLI for you. The site's OAuth app (`client_id`) mints
-visitor tokens only, which cover what a visitor may see and nothing here.
-
-## 1. The brief → the solutions
-
-Unchanged from SKILL.md step 2 and its Verticals table: the brief names the business, the table
-names the solutions it needs. Read each solution's `<TEMPLATES>/<solution>/INSTRUCTIONS.md` for
-what it covers and `<TEMPLATES>/<solution>/seed/SEED.md` for what a seeded site holds.
-
-## 2. The site
-
-The CLI's `npm create @wix/new` is one call: `POST /headless-business-setup/v1/headless-business/provision`,
-with `origin: agent-<your-id>`, a name, and the solutions to install as `seedOptions`. The recipe
-is `<MANAGE>/references/sites/create-headless-site.md`; it returns the `metaSiteId` and the
-site's OAuth client `appId`. Do not create a site any other way: a project from Create Project or
-a template is neither headless nor publishable, and a later run with a machine cannot attach to it.
-
-A site that already exists (the brief names it) is read first, never seeded unasked: SKILL.md
-step 2 and `<SKILL_ROOT>/guides/existing-site.md` apply as written.
-
-## 3. The apps
-
-A solution the provision call did not install, or a capability's app (Members Area, Forms,
-Restaurants, Donations, FAQ), goes on with the Apps Installer:
-`<MANAGE>/references/app-installation/install-wix-apps.md`. The app ids are in each
-`seed-<solution>.mjs`, which installs them before seeding.
-
-## 4. The seed
-
-`seed-<solution>.mjs` is a sequence of REST calls, and `SEED.md` is its contract: the plan shape
-(what to create, how many, which images), the order the entities need, and the traps the script
-encodes (a Bookings service needs a category to be visible and takes resource ids, not staff ids;
-a Forms field is registered by its `validation` block; a product's choice photos are linked after
-the gallery holds them). Read `SEED.md`, read the script for any call `SEED.md` only names, and make the same
-calls through `<MANAGE>`'s recipe for each (services, products, posts, events, collections). Keep
-the script's rules: create, never delete, and report what the site already held. Image prompts
-need the Media Manager; without it, products and services stay text-only, say so.
-
-## 5. The frontend
-
-The shipped `app/` code cannot be built here, and the Astro pages cannot be released. A page can
-still be shipped: one self-contained `index.html` that loads the Wix SDK from a package CDN and
-talks to the site as a visitor, dropped onto the site from step 2 through
-`<MANAGE>/references/sites/upload-static-site.md`. The kit's own frontend for this site is a run
-with a machine, which attaches to this site (`guides/existing-site.md`) rather than making a new one.
-
-**The page.** One file, a few hundred lines, written in full before the first drop: the drop takes
-the complete file set in one call, and a response has a hard size limit, so there is no second
-pass. The SDK comes from a pinned package URL, `https://esm.sh/@wix/sdk@<version>` and the
-solution's package (`@wix/bookings`, `@wix/stores`, `@wix/blog`, …); the client is
-`createClient({ modules: { … }, auth: OAuthStrategy({ clientId }) })` with the `appId` the provision
-call returned, and the SDK mints and refreshes the visitor token itself. Markup, a render function
-per state, the event handlers: that is what you write. Keep what the page shows to what the site
-holds; nothing invented, as in SKILL.md step 4.
-
-**The calls.** Take every SDK call's shape from the kit's own transport for the solution,
-`<TEMPLATES>/<solution>/app/wix/<solution>/*.ts` (`services.ts`, `booking.ts`, `catalog.ts`, …,
-with `<TEMPLATES>/shared/app/wix/sdk.ts` for the client wiring): those files call the same SDK
-modules the page imports, and they are verified. Copy the form of the call, not the file. The
-cores beside them (`*-core.ts`) hold the rules the page needs and nothing else does: which fields
-to read, how a price or a duration is formatted, which slot is bookable, how an id is read.
-
-**A call those files don't cover** is confirmed before it is written, the way `<DOCS>` describes:
-the method's SDK page, and when the page and the package disagree, the package's own type
-declarations (the `@wix/auto_sdk_<solution>_<module>` package the solution package depends on,
-its `index.d.ts`) are the truth. Two shapes that recur, as examples of what the types settle and
-the kit's files already encode: SDK query methods return a query builder finished with `.find()`;
-and an entity's id arrives as `_id` on some objects and `id` on others (the kit reads both,
-`rawId`). Dates travel as local
-wall-clock strings in the business time zone. A page cannot be run here, so a wrong shape fails
-silently in the browser; the file beside the skill is the check that is available.
-
-## 6. Closing
-
-As in SKILL.md step 5, minus the live URL when nothing was released: what exists on the site, by
-name; the dashboard link `https://manage.wix.com/dashboard/<metaSiteId>` and each solution's own
-pages from its INSTRUCTIONS.md table; what is placeholder; payments, when the site takes money;
-and what this run could not do, with the site id, so a run with a machine continues here.

package/skills/wix-manage/references/bookings/create-appointment-service.md

@@ -1,243 +0,0 @@
----
-name: "Create Appointment Service"
-description: "Create an appointment booking service — e.g. 'set up consultations', 'create a 1-on-1 session', 'add a personal training appointment', 'create a meeting service for $25'. Handles staff assignment (required), session duration, pricing, and 1-on-1 capacity defaults via bulkCreateServices API."
----
-
-# Create Appointment Service from Prompt
-
-## When to Use
-
-- User wants to create an appointment-based service: "set up consultations", "create a 1-on-1 session", "add a personal training appointment", "create a meeting service"
-- The service type is APPOINTMENT — customer picks an available time slot during staff working hours
-- For general service creation where the type is ambiguous, see [Create Booking Service from Prompt](./create-booking-service-from-prompt.md)
-
-## Prerequisites
-
-- For full API field definitions, validation rules, and troubleshooting, see [Create and Update Booking Services](./create-and-update-booking-services.md)
-
----
-
-## Step 1: Gather Business Context
-
-Run these queries to collect site data for informed defaults.
-
-### 1a. Query Staff Members (CRITICAL for Appointments)
-
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v1/staff-members/query' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{
-    "query": {},
-    "fields": ["RESOURCE_DETAILS"]
-  }'
-```
-
-Save each staff member's `resourceId` (not `id`). Note which one has `default: true`.
-
-**APPOINTMENT services REQUIRE at least one staff member.** If no staff members exist, create one first using [Bookings Staff Setup](./bookings-staff-setup.md).
-
-### 1b. Query Service Categories
-
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v2/categories/query' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{ "query": {} }'
-```
-
-### 1c. Query Existing Services (Duplicate Check)
-
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v2/services/query' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{ "query": { "paging": { "limit": 100 } } }'
-```
-
-Warn the user if a service with a similar name already exists.
-
----
-
-## Step 2: Apply Appointment Defaults
-
-For any fields the user did not explicitly specify:
-
-| Field | Default | Notes |
-|---|---|---|
-| Duration | 60 minutes | Set via `schedule.availabilityConstraints.sessionDurations` |
-| Capacity | 1 | Appointments are typically 1-on-1 |
-| Staff | Auto-assign | Use `default: true` staff, or first available |
-| Online booking | Enabled | `onlineBooking.enabled: true` |
-
-### Pricing (if not specified)
-
-- If user specifies a price → `rateType: "FIXED"`
-- If user says "free" → `rateType: "NO_FEE"`, `options.inPerson: true`, `options.online: false`
-- If no price mentioned → infer from context (consultations ~$50-100, sessions ~$30-60) or default to free
-
-### Staff Assignment
-
-- **1 staff member** → auto-assign using their `resourceId`
-- **Multiple staff members** → use the one with `default: true`, or the first one
-- **No staff members** → create one first using [Bookings Staff Setup](./bookings-staff-setup.md), then proceed
-
-### Category
-
-- If categories exist → assign the most relevant one
-- If no categories exist → create a "General" category:
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v2/categories' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{ "category": { "name": "General" } }'
-```
-
-### Service Name & Description
-
-- Use the user's wording for the service name
-- Generate a brief, professional description (1-2 sentences)
-
----
-
-## Step 3: Create the Appointment Service
-
-**Paid appointment:**
-
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v2/bulk/services/create' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{
-    "returnEntity": true,
-    "services": [{
-      "name": "<SERVICE_NAME>",
-      "description": "<GENERATED_DESCRIPTION>",
-      "type": "APPOINTMENT",
-
-      "onlineBooking": { "enabled": true },
-      "staffMemberIds": ["<RESOURCE_ID>"],
-      "schedule": {
-        "availabilityConstraints": {
-          "sessionDurations": [<DURATION_MINUTES>]
-        }
-      },
-      "payment": {
-        "rateType": "FIXED",
-        "options": { "online": true, "inPerson": false },
-        "fixed": {
-          "price": { "value": "<PRICE>" }
-        }
-      },
-      "category": {
-        "id": "<CATEGORY_ID>"
-      }
-    }]
-  }'
-```
-
-**Free appointment:**
-
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v2/bulk/services/create' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{
-    "returnEntity": true,
-    "services": [{
-      "name": "<SERVICE_NAME>",
-      "description": "<GENERATED_DESCRIPTION>",
-      "type": "APPOINTMENT",
-
-      "onlineBooking": { "enabled": true },
-      "staffMemberIds": ["<RESOURCE_ID>"],
-      "schedule": {
-        "availabilityConstraints": {
-          "sessionDurations": [<DURATION_MINUTES>]
-        }
-      },
-      "payment": {
-        "rateType": "NO_FEE",
-        "options": { "online": false, "inPerson": true }
-      },
-      "category": {
-        "id": "<CATEGORY_ID>"
-      }
-    }]
-  }'
-```
-
-### APPOINTMENT-Specific Reminders
-
-- `staffMemberIds` is **required** — uses `resourceId` values, not staff member `id`
-- `schedule.availabilityConstraints.sessionDurations` sets the appointment length
-- Availability is based on the assigned staff member's working hours schedule
-
-Save the `serviceId` from the response: `results[0].item.id` (the created service is directly under `item` — there is no `item.service`). This requires `returnEntity: true` on the request; without it the response carries only `results[0].itemMetadata.id`.
-
----
-
-## Step 4: Summary Message
-
-Provide a summary including:
-
-1. **What was created** — service name, price, duration, assigned staff member
-2. **Assumptions made** — list defaults used (e.g., "I set the duration to 60 minutes since you didn't specify")
-3. **Next steps** — "Click Save to finalize, then set up your availability"
-4. **Offer to adjust** — "Want me to change the price, duration, or staff assignment?"
-
-**Example:**
-
-> I created **"Strategy Consultation"**:
->
-> - **Type**: Appointment (1-on-1)
-> - **Price**: $75 per session
-> - **Duration**: 60 minutes
-> - **Staff**: Assigned to Sarah Johnson
-> - **Category**: Consulting
->
-> I assumed a 60-minute duration since you didn't specify. You can review and adjust the details in the service form.
-
----
-
-## Error Handling
-
-| Error | Cause | Action |
-|---|---|---|
-| 400 "staffMemberIds required" | No staff assigned | Query staff; if none exist, create one via [Bookings Staff Setup](./bookings-staff-setup.md) |
-| 400 "INVALID_PAYMENT_OPTIONS" | Payment misconfigured | Free: `inPerson: true`, `online: false`. Paid: price > 0 |
-| 403 | Permission denied | Inform user they lack permission |
-
----
-
-## Payment Validation Quick Reference
-
-| rateType | `options.online` | `options.inPerson` | Valid? |
-|----------|------------------|-------------------|--------|
-| FIXED    | true             | false             | ✓      |
-| FIXED    | false            | true              | ✓      |
-| FIXED    | true             | true              | ✓      |
-| NO_FEE   | false            | true              | ✓      |
-| NO_FEE   | true             | false             | ✗      |
-| Any      | false            | false             | ✗      |
-
----
-
-## What This Skill Does NOT Cover
-
-- **Schedule/availability setup** — staff working hours need separate configuration. See [Bookings Staff Setup](./bookings-staff-setup.md)
-- **Pricing plans** — memberships and session packs are separate. See [Create and Update Pricing Plans](../pricing-plans/create-and-update-pricing-plans.md)
-- **Service images** — requires Media Manager API (see [create-and-update-booking-services.md](./create-and-update-booking-services.md))
-
----
-
-## API Documentation Reference
-
-- [Bulk Create Services](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/bulk-create-services)
-- [Query Services](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/query-services)
-- [Query Categories](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/categories-v2/query-categories)
-- [Create Category](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/categories-v2/create-category)
-- [Query Staff Members](https://dev.wix.com/docs/api-reference/business-solutions/bookings/staff-members/staff-members/query-staff-members)
-- [Create Staff Member](https://dev.wix.com/docs/api-reference/business-solutions/bookings/staff-members/staff-members/create-staff-member)
-- [About Service Types](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/about-service-types)
-- [About Service Payments](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/about-service-payments)

package/skills/wix-manage/references/bookings/create-booking-service-from-prompt.md

@@ -1,31 +0,0 @@
----
-name: "Create Booking Service from Prompt"
-description: "Create a booking service from a user prompt — e.g. 'create a yoga class for $50', 'set up consultations for $75', 'add a personal training appointment', 'create a 6-week photography workshop', 'create a hidden free test course with 8 online sessions'. Determines the service type (APPOINTMENT, CLASS, or COURSE) and delegates to the type-specific recipe. For COURSE services with session dates/counts, follow the course recipe's separate Calendar bulkCreateEvents step; Services V2 alone does not create bookable course sessions."
----
-
-# Create Booking Service from Natural Language Prompt
-
-## When to Use
-
-- User describes a service they want to create using natural language (e.g., "create a yoga class for $50", "set up consultation sessions", "add a personal training appointment", "create a hidden free test course with 8 online sessions")
-- The intent is autonomous creation — fill in reasonable defaults rather than asking the user for every field
-
-## Step 1: Determine Service Type
-
-| User mentions | Type | Recipe |
-|---|---|---|
-| consultation, appointment, meeting, 1-on-1, one-on-one, session | `APPOINTMENT` | [Create Appointment Service](./create-appointment-service.md) |
-| class, yoga, pilates, group session, group workout, bootcamp class | `CLASS` | [Create Class Service](./create-class-service.md) |
-| workshop, program, course, training program, multi-session, fixed series, 8 sessions | `COURSE` | [Create Course Service](./create-course-service.md) |
-| (unclear or unspecified) | `APPOINTMENT` | [Create Appointment Service](./create-appointment-service.md) |
-
-## Step 2: Follow the Type-Specific Recipe
-
-Once the service type is determined, follow the corresponding recipe linked above. Each recipe covers:
-
-1. Gathering business context (staff where required, categories, duplicate check)
-2. Applying type-specific defaults (pricing, capacity, duration, staff assignment)
-3. Creating the service via `bulkCreateServices`
-4. For COURSE services with session dates/counts, creating separate Calendar events via `bulkCreateEvents` on the returned `service.schedule.id`
-5. Navigating to the service form for user review
-6. Providing a summary of what was created and assumptions made

package/skills/wix-manage/references/bookings/create-class-service.md

@@ -1,222 +0,0 @@
----
-name: "Create Class Service"
-description: "Create a class booking service — e.g. 'create a yoga class for $50', 'set up a pilates class', 'add a group fitness session', 'create a weekly meditation class'. Handles group capacity, recurring session defaults, and pricing via bulkCreateServices API. Staff assignment is not used for classes."
----
-
-# Create Class Service from Prompt
-
-## When to Use
-
-- User wants to create a group class: "create a yoga class", "set up a pilates class", "add a group fitness session", "create a weekly meditation class"
-- The service type is CLASS — a single event or recurring series that multiple customers can book
-- Customers can sign up for one, several, or all sessions in a class series
-- For general service creation where the type is ambiguous, see [Create Booking Service from Prompt](./create-booking-service-from-prompt.md)
-
-## Prerequisites
-
-- For full API field definitions, validation rules, and troubleshooting, see [Create and Update Booking Services](./create-and-update-booking-services.md)
-
----
-
-## Step 1: Gather Business Context
-
-Run these queries to collect site data for informed defaults.
-
-### 1a. Query Service Categories
-
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v2/categories/query' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{ "query": {} }'
-```
-
-### 1b. Query Existing Services (Duplicate Check)
-
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v2/services/query' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{ "query": { "paging": { "limit": 100 } } }'
-```
-
-Warn the user if a service with a similar name already exists.
-
-> **Note:** Staff queries are optional for CLASS services since `staffMemberIds` is ignored by the API. However, querying staff can still be useful for context (e.g., mentioning instructors in the description).
-
----
-
-## Step 2: Apply Class Defaults
-
-For any fields the user did not explicitly specify:
-
-| Field | Default | Notes |
-|---|---|---|
-| Capacity | 10 | `defaultCapacity` — required for CLASS |
-| Online booking | Enabled | `onlineBooking.enabled: true` |
-
-### Pricing (if not specified)
-
-- If user specifies a price → `rateType: "FIXED"` (per session)
-- If user says "free" → `rateType: "NO_FEE"`, `options.inPerson: true`, `options.online: false`
-- If no price mentioned → infer from context (yoga/fitness classes ~$15-30, art/music ~$20-40) or default to free
-
-### Capacity (if not specified)
-
-- Default: 10 participants
-- If user mentions capacity (e.g., "small group of 6", "up to 20") → use their number
-- Typical ranges: small group 4-8, standard 10-20, large 20-50
-
-### Category
-
-- If categories exist → assign the most relevant one (e.g., "Fitness", "Wellness")
-- If no categories exist → create one:
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v2/categories' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{ "category": { "name": "General" } }'
-```
-
-### Service Name & Description
-
-- Use the user's wording for the service name
-- Generate a brief, professional description (1-2 sentences) mentioning it's a group class
-
----
-
-## Step 3: Create the Class Service
-
-**CRITICAL: CLASS services do NOT use `staffMemberIds` or `sessionDurations`.** These fields are ignored. Use `defaultCapacity` instead.
-
-**Paid class:**
-
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v2/bulk/services/create' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{
-    "returnEntity": true,
-    "services": [{
-      "name": "<SERVICE_NAME>",
-      "description": "<GENERATED_DESCRIPTION>",
-      "type": "CLASS",
-
-      "onlineBooking": { "enabled": true },
-      "defaultCapacity": <CAPACITY>,
-      "payment": {
-        "rateType": "FIXED",
-        "options": { "online": true, "inPerson": false },
-        "fixed": {
-          "price": { "value": "<PRICE>" }
-        }
-      },
-      "category": {
-        "id": "<CATEGORY_ID>"
-      }
-    }]
-  }'
-```
-
-**Free class:**
-
-```bash
-curl -X POST 'https://www.wixapis.com/bookings/v2/bulk/services/create' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{
-    "returnEntity": true,
-    "services": [{
-      "name": "<SERVICE_NAME>",
-      "description": "<GENERATED_DESCRIPTION>",
-      "type": "CLASS",
-
-      "onlineBooking": { "enabled": true },
-      "defaultCapacity": <CAPACITY>,
-      "payment": {
-        "rateType": "NO_FEE",
-        "options": { "online": false, "inPerson": true }
-      },
-      "category": {
-        "id": "<CATEGORY_ID>"
-      }
-    }]
-  }'
-```
-
-### CLASS-Specific Reminders
-
-- Do **NOT** include `staffMemberIds` — it is ignored for CLASS services
-- Do **NOT** include `schedule.availabilityConstraints.sessionDurations` — not used for CLASS
-- `defaultCapacity` is **required** — sets max participants per session
-- After creation, class sessions must be scheduled separately via `bulkCreateEvents` using the returned `service.schedule.id` (see [Create and Update Booking Services](./create-and-update-booking-services.md))
-
-**Response:** Save the service ID from `results[0].item.id` and the schedule ID for `bulkCreateEvents` from `results[0].item.schedule.id` (the created service is directly under `item`). This requires `returnEntity: true` on the request — without it the response carries only `results[0].itemMetadata.id`, which has no `schedule.id`.
-
----
-
-## Step 4: Summary Message
-
-Provide a summary including:
-
-1. **What was created** — service name, price per session, capacity
-2. **Assumptions made** — list defaults used (e.g., "I set the capacity to 10 participants since you didn't specify")
-3. **Schedule note** — remind the user that class sessions still need to be scheduled
-4. **Next steps** — "Click Save to finalize, then set up the class schedule"
-5. **Offer to adjust** — "Want me to change the price, capacity, or description?"
-
-**Example:**
-
-> I created **"Vinyasa Yoga Class"**:
->
-> - **Type**: Class (group session)
-> - **Price**: $25 per session
-> - **Capacity**: 10 participants
-> - **Category**: Fitness
->
-> I assumed a capacity of 10 since you didn't specify. You can review and adjust the details in the service form.
->
-> **Next step:** You'll need to set up the class schedule (days and times) in the service form.
-
----
-
-## Error Handling
-
-| Error | Cause | Action |
-|---|---|---|
-| 400 "INVALID_PAYMENT_OPTIONS" | Payment misconfigured | Free: `inPerson: true`, `online: false`. Paid: price > 0 |
-| 403 | Permission denied | Inform user they lack permission |
-
----
-
-## Payment Validation Quick Reference
-
-| rateType | `options.online` | `options.inPerson` | Valid? |
-|----------|------------------|-------------------|--------|
-| FIXED    | true             | false             | ✓      |
-| FIXED    | false            | true              | ✓      |
-| FIXED    | true             | true              | ✓      |
-| NO_FEE   | false            | true              | ✓      |
-| NO_FEE   | true             | false             | ✗      |
-| Any      | false            | false             | ✗      |
-
----
-
-## What This Skill Does NOT Cover
-
-- **Class schedule setup** — recurring events (days/times) must be configured separately via Calendar Events API. See [Create and Update Booking Services](./create-and-update-booking-services.md) Step 3.
-- **Pricing plans** — memberships and class packs are separate. See [Create and Update Pricing Plans](../pricing-plans/create-and-update-pricing-plans.md)
-- **Instructor assignment** — `staffMemberIds` is ignored for CLASS. Staff association is managed through calendar events.
-- **Service images** — requires Media Manager API (see [create-and-update-booking-services.md](./create-and-update-booking-services.md))
-
----
-
-## API Documentation Reference
-
-- [Bulk Create Services](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/bulk-create-services)
-- [Query Services](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/query-services)
-- [Query Categories](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/categories-v2/query-categories)
-- [Create Category](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/categories-v2/create-category)
-- [Bulk Create Events](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/bulk-create-event)
-- [About Service Types](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/about-service-types)
-- [About Service Payments](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/about-service-payments)