@wix/agent-skills 1.31.0 → 1.31.2

package/skills/wix-manage/references/automations/activation-status.md

@@ -0,0 +1,52 @@
+---
+name: "Automations Activation Status"
+description: "Read an automation’s current ACTIVE or INACTIVE status and distinguish it from historical run outcomes."
+---
+
+# Inspect activation status
+
+An automation's current state is `configuration.status`: ACTIVE is eligible for new trigger
+events; INACTIVE is not. Neither value proves that a historical run succeeded or that a
+pending activation has stopped.
+
+1. Resolve the requested name with one Query Automations call filtered by that exact name
+   (below); don't page through other automations. If the ID is already supplied, go to Get.
+   If several match, open your answer by listing each match's full returned ID and asking
+   which one the user means; don't report a single status. If none match, say so and ask the
+   user to check the name or site; never guess an ID.
+2. Get the matching returned ID and read `configuration.status`.
+3. Answer briefly and completely in one reply. Start with the automation's exact name, its
+   returned ID and ACTIVE/INACTIVE from that response, then say what it means for new trigger
+   events. If the user asks whether the status says anything about past runs, answer it
+   directly in the next sentence: status does not show whether past runs succeeded; they are
+   visible in the automation's activity view in the site dashboard.
+4. If Get returns not found, do not state a status. Open with: the automation wasn't found on
+   this site, so its status can't be determined, and ask the user to confirm the site and the
+   automation ID. This question is required. Then give the possible causes below.
+
+Use an authorized site-scoped client with Set Up Automations permission. REST calls use
+`Authorization: <token>`. An API key also needs `wix-site-id: <metaSiteId>`; do not combine it
+with `wix-account-id`. Never print credentials.
+
+`POST https://www.wixapis.com/automations-service/v2/automations/query`
+
+```json
+{"query":{"filter":{"name":"<automation name>"},"cursorPaging":{"limit":25}}}
+```
+
+Read `automations[]` and `pagingMetadata.cursors.next`; continue pages if needed. Retain the
+returned `id` and exact name. Then:
+
+`GET https://www.wixapis.com/automations-service/v2/automations/<automationId>`
+
+Read `automation.configuration.status` from the Get response. Never infer status from the
+name or a previous mutation. Do not validate, change configuration, toggle status or test-run
+an automation to answer this read-only request.
+
+Not-found causes (step 4): unpublished builder drafts do not appear
+through this API, but a 404 can also mean deletion or a changed ID after overriding a
+preinstalled automation. When the user's history supports an unpublished builder draft as the
+cause, ask the owner to publish or discard it rather than reproducing its edits.
+
+Official contracts: [Query Automations](https://dev.wix.com/docs/api-reference/business-management/automations/automations/automations-v2/query-automations),
+[Get Automation](https://dev.wix.com/docs/api-reference/business-management/automations/automations/automations-v2/get-automation).

package/skills/wix-manage/references/automations/api-catalog.md

@@ -0,0 +1,81 @@
+---
+name: "Automations API Catalog"
+description: "Discover installed automation triggers and actions and inspect their schemas through site-scoped public catalog APIs."
+---
+
+# Discover installed automation capabilities
+
+Check the site's installed trigger/action catalogs, then inspect the chosen components'
+schemas. This recipe is read-only: do not create an automation, install an app, generate email
+content, or run an action to establish availability.
+
+## Authentication
+
+Use an authorized site-scoped client with Set Up Automations permission. REST calls use
+`Authorization: <token>`. An API key also needs `wix-site-id: <metaSiteId>`; do not combine it
+with `wix-account-id`. OAuth app tokens are bound to a site instance. Never print credentials.
+A 401/403 is an access failure, not evidence that a catalog component is unavailable.
+
+## Resolve, select, inspect
+
+1. Use a known key only as a search hint. Resolve an exact candidate first; if it is absent,
+   browse small pages and compare names/semantics locally. Do not conclude that a remembered
+   key exists on this site without a successful Resolve response.
+2. For triggers, request `basicFieldsOnly: true` while browsing, then hydrate only the chosen
+   trigger with Get Trigger By App Id And Key. Compare its payload and filters to the intent.
+3. Actions already include schemas in Resolve. Retain the chosen returned identity and
+   required input fields; avoid repeating the whole catalog just to read display names.
+4. Summarize the available pair and required configuration, distinguishing what the trigger
+   supplies from values the user would need to choose. Do not mutate anything to prove it.
+
+### Trigger discovery
+
+`POST https://www.wixapis.com/v1/triggers/resolve`
+
+```json
+{"basicFieldsOnly":true,"query":{"filter":{"triggerKey":"contacts-new_contact_was_created"},"paging":{"limit":25,"offset":0}}}
+```
+
+Read `results[]` and `paging`. A nonempty matching result establishes an installed trigger;
+use its returned `appId` and `triggerKey` in:
+
+`GET https://www.wixapis.com/v1/triggers/apps/<appId>/keys/<triggerKey>`
+
+Read `trigger.payloadDataSchema`, `trigger.filters` and `trigger.automationConfigSchema`.
+The contact-created key above is a discovery hint; names and availability may vary by site.
+
+### Action discovery
+
+`POST https://www.wixapis.com/v1/actions/resolve`
+
+```json
+{"query":{"filter":{"actionKey":"addLabelsToContact"},"paging":{"limit":25,"offset":0}}}
+```
+
+Read `actions[]`, `paging`, and each chosen action's `appId`, `actionKey`, `inputSchema`,
+`outputSchema` and `interfaceConfiguration`. Inspect required properties, types, enums and
+field descriptions before explaining configuration. For an existing runtime version use
+`GET https://www.wixapis.com/v1/actions/apps/<appId>/keys/<actionKey>` and read `action`.
+A site may have Add label to contact without Create task; never substitute one for the other.
+
+### Bounded fallback
+
+Remove the exact-key filter to browse; use offset pages of at most 25 entries, with no sort.
+Resolve Actions has no `basicFieldsOnly` option and rejects displayName filters; search names
+locally. Compact each page to identities and display names before adding it to reasoning
+context. Fetch each catalog page and static schema once, cache it for this site, and hydrate only a
+shortlist; never re-fetch a page or schema you already have. Pages can overlap;
+de-duplicate by appId+key. Only a complete scan with distinct count equal to `paging.total`
+proves absence; state the evidence ("scanned N distinct of `paging.total` N"). Without that
+proof, say the component was "not found in the installed catalog", never that it is not
+installed. Either way, list the closest related actions you saw in that scan, as findings
+rather than substitutes, with their returned `appId`/`actionKey` and display name; don't fetch
+their schemas unless the user asks.
+
+Resolve is site-scoped; global Query catalogs can include uninstalled apps and do not prove
+availability. The method schemas below confirm the full public URLs; do not invent a private
+transport or guess a new path if access fails.
+
+Official contracts: [Resolve Triggers](https://dev.wix.com/docs/api-reference/business-management/automations/triggers/trigger-catalog/resolve-triggers),
+[Resolve Actions](https://dev.wix.com/docs/api-reference/business-management/automations/actions/action-catalog/resolve-actions).
+For current automation status use [Automations Activation Status](https://dev.wix.com/docs/api-reference/business-management/automations/skills/automations-activation-status).

package/skills/wix-manage/references/automations/build-and-manage-automations.md

@@ -0,0 +1,34 @@
+---
+name: "Build and Manage Wix Automations"
+description: "Discover installed automation triggers and actions and inspect an automation’s current active status without changing site data."
+---
+
+# Build and Manage Wix Automations
+
+Use this guide to discover installed automation capabilities and inspect whether an
+automation is active. These are read-only workflows. Creation, configuration edits,
+activation and test execution are outside what this skill covers.
+Do not perform a write when the user asks only to inspect.
+
+| Request | Load |
+| --- | --- |
+| Check which triggers/actions are available and what inputs they need | [Automations API Catalog](https://dev.wix.com/docs/api-reference/business-management/automations/skills/automations-api-catalog) |
+| Is an automation turned on? What does its status mean? | [Automations Activation Status](https://dev.wix.com/docs/api-reference/business-management/automations/skills/automations-activation-status) |
+
+For a capability check, resolve the site's catalogs, retain the returned app/key identities,
+and inspect the selected schemas. A remembered action key is a search hint, not evidence that
+the action is installed. State missing prerequisites without offering an unverified substitute.
+If a requested action isn't found, report it exactly as the "Bounded fallback" section of
+[Automations API Catalog](https://dev.wix.com/docs/api-reference/business-management/automations/skills/automations-api-catalog) says (scan evidence, "not found" vs "not installed", closest
+related actions).
+Resolve the trigger once and scan the action catalog once; answer from those results instead
+of repeating either call.
+
+For current status, find the exact automation, Get its returned ID, and report the status
+from that response. Every status answer names the automation and its returned ID. Current ACTIVE/INACTIVE status is separate from historical run results.
+
+Status questions need only Query and Get Automation: don't call the trigger or action catalogs
+for them. Query by the exact name with one bounded page before paging further.
+
+Keep the requested site context fixed. Do not expose tokens or credentials. Tie every claim
+to the returned data, and distinguish a missing record from proof of nonexistence.

package/skills/wix-manage/references/bookings/booking-service-policy-setup.md

@@ -5,6 +5,9 @@ description: Sets up booking policies, cancellation rules, and waitlist configur
 
 # Technical Step-by-Step Instructions: Configuring Wix Bookings Service Policies (Real-World, API-First)
 
+> These calls need the Wix Bookings app on the site (`appDefId` `13d21c63-b5ec-5912-8397-c3a5ddb27a97`); a `428`, a `400` naming the app, or an empty result on a site that should have content means it is not there. [List Installed Apps](../app-installation/list-installed-apps.md) shows what the site has; [Install Wix Apps](../app-installation/install-wix-apps.md) adds it by that id.
+
+
 ## Description
 
 Below are the recommended steps to successfully configure booking, cancellation, and waitlist policies for Wix Bookings services. This recipe covers policy inheritance, service-specific overrides, and common policy configurations for different business models.