@wix/agent-skills 1.36.0 → 1.36.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/agent-skills",
-  "version": "1.36.0",
+  "version": "1.36.1",
   "description": "Wix Skills for AI coding agents — versioned npm distribution of the wix/skills content.",
   "license": "MIT",
   "repository": {
@@ -15,8 +15,13 @@
     "version": "node .github/scripts/sync-plugin-versions.mjs && git add .claude-plugin/plugin.json .codex-plugin/plugin.json .cursor-plugin/plugin.json plugin.json gemini-extension.json antigravity/wix/plugin.json skills/wix-headless-kit/install/pins.json"
   },
   "files": [
-    "skills/**",
-    "!skills/wix-headless-cold-start/**",
+    "skills/wix-app/**",
+    "skills/wix-design-system/**",
+    "skills/wix-docs/**",
+    "skills/wix-headless-kit/**",
+    "skills/wix-headless-templates/**",
+    "skills/wix-manage/**",
+    "skills/wix-readme/**",
     "README.md",
     "LICENSE"
   ],

package/skills/wix-headless-kit/install/pins.json

@@ -3,6 +3,6 @@
   "@wix/create-new": "0.0.124",
   "typescript": "5.8.3",
   "templates": {
-    "ref": "v1.36.0"
+    "ref": "v1.36.1"
   }
 }

package/skills/wix-manage/SKILL.md

@@ -343,11 +343,11 @@ Import Google Business Profile locations into the authenticated Wix site, list a
 
 ## Marketing
 
-### [Create and Publish a Social Media Post (with AI generation)](references/marketing/create-and-publish-social-post.md)
-"End-to-end flow to create a social media post, optionally generating it with AI, and publish or schedule it to a site's connected channel (Instagram, Facebook, LinkedIn, X/Twitter, TikTok, Pinterest, YouTube, Google Business Profile) using the Wix Publisher API. Can generate a full per-channel post from a free-text idea or from the site's own assets (products, blog posts, events, bookings, coupons, categories), generate caption/title suggestions, and edit an existing image with AI. Settles the post content with you first, then confirms the channel is connected, checks premium quota, creates a draft, and publishes now or schedules it. Use for 'create a post', 'generate a post from my product/idea', 'write a caption', 'caption ideas/suggestions', 'edit a post image with AI', 'post to Instagram/Facebook/TikTok', 'connect my Instagram/Pinterest/LinkedIn', or 'schedule a post'."
+### [Create and Publish a Social Media Post](references/marketing/create-and-publish-social-post.md)
+"End-to-end flow to create a social media post, with its text written for you or your own, and publish or schedule it to a site's connected channel (Instagram, Facebook, LinkedIn, X/Twitter, TikTok, Pinterest, YouTube, Google Business Profile) using the Wix Publisher API. Can write a full per-channel post from a free-text idea or from the site's own assets (products, blog posts, events, bookings, coupons, categories), with your own image, and suggest captions and titles. Settles the post content with you first, then confirms the channel is connected, checks premium quota, creates a draft, and publishes now or schedules it. Use for 'create a post', 'generate a post from my product/idea', 'write a caption', 'caption ideas/suggestions', 'post to Instagram/Facebook/TikTok', 'connect my Instagram/Pinterest/LinkedIn', or 'schedule a post'."
 
 ### [Generate a Marketing Plan and Schedule Its Posts](references/marketing/generate-and-publish-marketing-plan.md)
-"End-to-end flow to generate an AI-powered social media marketing plan for a site and schedule its generated posts for publishing, using the Wix Marketing Plan API. Recommends configuring marketing settings (goal, tone, cadence, content pillars) before the first generation, generates the plan asynchronously, polls until it's ready, then schedules the DRAFT posts. Includes generating posts for additional activities. Use for 'generate a marketing plan', 'create a social media plan/calendar', or 'schedule my plan's posts' requests."
+"End-to-end flow to generate a site's social media marketing plan with the Wix Marketing Plan API and schedule the post drafts it returns. Recommends configuring marketing settings (goal, tone, cadence, content pillars) before the first generation, generates the plan asynchronously, polls until it's ready, then schedules the DRAFT posts. Includes generating posts for additional activities. Use for 'generate a marketing plan', 'create a social media plan/calendar', or 'schedule my plan's posts' requests."
 
 ### [Marketing Dashboard Navigation](references/marketing/marketing-dashboard-navigation.md)
 "Builds direct links to Wix marketing dashboard pages on manage.wix.com — the social posts hub (drafts, scheduled and published posts across connected channels), post design templates, saved designs, and the email marketing pages (campaigns list, campaign templates, campaign analytics). Pairs each main marketing entity (social post item, connected social account, marketing-plan post, email campaign) with its read API so you can fetch an entity and hand back a 'view it in your dashboard' link. Use when the user asks where something is in the Wix dashboard, wants a direct link to a dashboard page, or you need a dashboard URL to include with the result of an API operation."

package/skills/wix-manage/references/cms/cms-data-items-crud.md

@@ -37,6 +37,83 @@ It may be, that user refers to schema by its `displayName` rather than `id`, if
 
 ---
 
+## Writing Image Fields
+
+Read the collection schema before setting an image: `IMAGE` takes an HTTP URL or
+`wix:image://` string; `MEDIA_IMAGE` takes a structured object. Never put a bare media ID,
+a URL string, or an editor media-search result directly into a `MEDIA_IMAGE` field.
+The API can return 200 and store an invalid string unchanged; an identical read-back
+is not proof that the image can render.
+
+1. Reuse the selected image if it is already in the site's Media Manager. For a new
+   external image, follow [Upload Media to Wix](../media/upload-media-to-wix.md).
+   If the user requested a generated image, first follow
+   [Generate an Image with AI](../media/generate-image-with-ai.md), then import it.
+   Confirm before importing or changing site data unless the user already authorized it.
+2. Build the field value from the Media Manager file descriptor: use
+   `file.media.image.image` for image metadata, with `file.id`, `file.url`, and
+   `file.displayName` as fallbacks for the ID, URL, and filename. Import can return
+   `PENDING` without image metadata; fetch the ready descriptor using the upload
+   recipe before using dimensions. Do not invent IDs or dimensions.
+3. For a Wix-hosted image, preserve `id`, `url`, `width`, `height`, `filename`, and
+   `altText` when available, and include a full `uri`:
+   `wix:image://v1/{id}/{encodedFilename}#originWidth={width}&originHeight={height}`.
+   An editor search result's `uri` may be only a media ID; resolve its file descriptor
+   and build the CMS value rather than copying that result. An external image may
+   instead use `{ "url": "https://example.com/photo.jpg", "altText": "Photo" }`;
+   not every supported object requires all the Wix-hosted metadata.
+4. Insert the object under `dataItem.data.<fieldKey>`, or patch an existing item
+   with `SET_FIELD` as below. For `IMAGE`, use the image URL or full Wix URI string
+   instead of the object. Leave the collection's existing field type unchanged.
+5. Read the item back and check the field against its declared type: for
+   `MEDIA_IMAGE`, require an object with a usable image source and the intended
+   image identity, not a string echoed by the API. Preserve unrelated item fields.
+   When browser access is available, check the image in the CMS or bound view.
+   Otherwise report that the structured value was saved and that rendering was
+   not visually verified. If generation or import fails, report the missing image;
+   do not write a placeholder or claim it was added.
+
+**Example — replace only the `image` field on an existing item**:
+
+`PATCH https://www.wixapis.com/wix-data/v2/items/{dataItemId}`
+
+The values below stand for metadata from the selected file, not values to fabricate.
+
+```json
+{
+  "dataCollectionId": "Milkshakes",
+  "patch": {
+    "dataItemId": "<dataItemId>",
+    "fieldModifications": [
+      {
+        "fieldPath": "image",
+        "action": "SET_FIELD",
+        "setFieldOptions": {
+          "value": {
+            "id": "<mediaId>",
+            "url": "https://static.wixstatic.com/media/<mediaId>",
+            "uri": "wix:image://v1/<mediaId>/Rainbow.jpg#originWidth=1024&originHeight=1024",
+            "filename": "Rainbow.jpg",
+            "width": 1024,
+            "height": 1024,
+            "altText": "Rainbow milkshake"
+          }
+        }
+      }
+    ]
+  }
+}
+```
+
+Verify with `GET https://www.wixapis.com/wix-data/v2/items/{dataItemId}?dataCollectionId=Milkshakes`
+and inspect `dataItem.data.image`.
+
+References: [Patch Data Item](https://dev.wix.com/docs/api-reference/business-solutions/cms/data-items/patch-data-item),
+[Import File](https://dev.wix.com/docs/api-reference/assets/media/media-manager/files/import-file),
+and [Importing Files](https://dev.wix.com/docs/api-reference/assets/media/media-manager/files/importing-files).
+
+---
+
 ## Insert Data Item
 
 **Endpoint**: `POST https://www.wixapis.com/wix-data/v2/items`
@@ -612,7 +689,7 @@ The method article documents the same expansion as `"includeReferences": [{ "fie
 | `IMAGE` | Image reference (HTTP url or wix:image://v1/{mediaId}/{friendlyName}) | `"wix:image://v1/3f72369f2219e2ee853e9e3df0217ce1.jpg/Colorful%20Business%20Cards.jpg"` |
 | `VIDEO` | Video reference (HTTP url or wix:video://v1/{mediaId}/{friendlyName}) | `"wix:video://v1/11062b_484182533ede4b9a81329daf20238867/Sketching%20Design%20Concepts#posterUri=11062b_484182533ede4b9a81329daf20238867f000.jpg&posterWidth=1920&posterHeight=1080"` |
 | `DOCUMENT` | Document reference  (HTTP url or wix:document://v1/{mediaId}) | `"wix:document://v1/..."` |
-| `MEDIA_IMAGE` | Wix Media Image | `{ "id": "<mediaId>", "url": "http://...", "height": 640, "width": 480, "altText": "Picture" }` |
+| `MEDIA_IMAGE` | Structured image object, never a bare ID or URL string; see [Writing Image Fields](cms-data-items-crud.md#writing-image-fields) | `{ "id": "<mediaId>", "url": "https://static.wixstatic.com/media/<mediaId>", "uri": "wix:image://v1/<mediaId>/Photo.jpg#originWidth=480&originHeight=640", "height": 640, "width": 480, "altText": "Picture" }` |
 | `MEDIA_VECTOR_ART` | Wix Media Vector Art | `{ "uri": "wix:vector://v1/...", "viewBox": "0 0 100 100", "contentType": "shape", "svgContent": "<svg>...</svg>" }` |
 | `URL` | Web URL | `"https://example.com"` |
 | `RICH_TEXT` | HTML content | `"<p>Rich text</p>"` |

package/skills/wix-manage/references/google-ads/create-performance-max-campaign.md

@@ -4,7 +4,7 @@ description: "Creates and launches a Google Ads Performance Max (PMAX) campaign
 ---
 # RECIPE: Create and Launch a Performance Max Campaign
 
-A **Performance Max (PMAX)** campaign runs across every Google channel from a single **asset group** — a bundle of headlines, descriptions, images, and (optionally) videos that Google mixes into ads. There are three flavors, set by `campaignType`:
+A **Performance Max (PMAX)** campaign runs across every Google channel from a single **asset group** — a bundle of headlines, descriptions, and images that Google mixes into ads. There are three flavors, set by `campaignType`:
 
 - **`PERFORMANCE_MAX`** — general multi-channel campaign.
 - **`PERFORMANCE_MAX_LEADS`** — lead-gen variant (phone/form conversions, search-theme signals, negative keywords, a ~28-day learning phase). **Requires** at least one asset group with headlines, descriptions, and images; assets are validated synchronously, so bad assets fail the create call immediately.
@@ -110,19 +110,19 @@ Use `recommendedBudgetAmountMicros` as `budget.amountMicros`, or present the `bu
 
 ## Assemble & create the campaign (in PAUSED)
 
-An **asset group** lives at `performanceMaxCampaign.assetGroups[]`. Its creative assets go under `assetGroupAssets.assets[]` — each asset sets **exactly one** payload field plus its `assetFieldType`. For a PMAX Leads asset group, meet Google's minimums or the create call fails with `NOT_ENOUGH_ASSETS`:
+An **asset group** lives at `performanceMaxCampaign.assetGroups[]`. Its creative assets go under `assetGroupAssets.assets[]` — each asset sets **exactly one** payload field plus its `assetFieldType`. For a PMAX Leads asset group, keep each asset type within its count below, or the create call fails with `INVALID_ASSET_GROUP_ASSETS`:
 
 | Asset | Payload field | `assetFieldType` | Count | Max chars |
 | --- | --- | --- | --- | --- |
 | Short headline | `headlineAsset.text` | `HEADLINE` | 3–15 | 30 |
-| Long headline | `longHeadlineAsset.text` | `LONG_HEADLINE` | exactly 1 | 90 |
-| Description | `descriptionAsset.text` | `DESCRIPTION` | 2–4 | 90 |
+| Long headline | `longHeadlineAsset.text` | `LONG_HEADLINE` | 1–5 | 90 |
+| Description | `descriptionAsset.text` | `DESCRIPTION` | 2–5 | 90 |
 | Business name | `businessNameAsset.text` | `BUSINESS_NAME` | exactly 1 | 25 |
-| Landscape image (1.91:1) | `imageAsset.{name,url}` | `MARKETING_IMAGE` | ≥1 | — |
-| Square image (1:1) | `imageAsset.{name,url}` | `SQUARE_MARKETING_IMAGE` | ≥1 | — |
-| Logo (1:1) | `imageAsset.{name,url}` | `LOGO` | ≥1 | — |
-| CTA button | `callToActionSelectionAsset.callToAction` | `CALL_TO_ACTION_SELECTION` | optional | `LEARN_MORE` \| `SHOP_NOW` \| `SIGN_UP` \| `CONTACT_US` |
-| YouTube video | `youtubeVideoAsset.{title,id}` | `YOUTUBE_VIDEO` | optional (1–5) | 11-char video id |
+| Landscape image (1.91:1) | `imageAsset.{name,url}` | `MARKETING_IMAGE` | 1–20 | — |
+| Square image (1:1) | `imageAsset.{name,url}` | `SQUARE_MARKETING_IMAGE` | 1–20 | — |
+| Logo (1:1) | `imageAsset.{name,url}` | `LOGO` | 1–5 | — |
+
+Call-to-action, YouTube video, and media bundle assets are not supported — leave them out of the asset group.
 
 Image `url` must be a Wix Media Manager URL (`static.wixstatic.com`) — the STEP 2 generated images already are; for other images, upload via the Media Manager first (see [Upload Media to Wix](../media/upload-media-to-wix.md)). Search themes go under `assetGroupSignals.signals[]` (PMAX Leads).
 
@@ -155,7 +155,7 @@ curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/campaigns' \
             { "businessNameAsset": { "text": "Sunrise Bakery" }, "assetFieldType": "BUSINESS_NAME" },
             { "imageAsset": { "name": "storefront-banner", "url": "https://static.wixstatic.com/media/abc123.jpg" }, "assetFieldType": "MARKETING_IMAGE" },
             { "imageAsset": { "name": "product-square",    "url": "https://static.wixstatic.com/media/def456.jpg" }, "assetFieldType": "SQUARE_MARKETING_IMAGE" },
-            { "callToActionSelectionAsset": { "callToAction": "SHOP_NOW" }, "assetFieldType": "CALL_TO_ACTION_SELECTION" }
+            { "imageAsset": { "name": "bakery-logo",       "url": "https://static.wixstatic.com/media/ghi789.png" }, "assetFieldType": "LOGO" }
           ] },
           "assetGroupSignals": { "signals": [
             { "searchTheme": { "text": "artisan bakery" } },
@@ -192,7 +192,7 @@ Returns the campaign with an updated `status`. Ads begin serving across Google c
 | --- | --- | --- |
 | `ACCOUNT_NOT_FOUND` | No Google Ads account | Run [install-and-create-account](install-and-create-account.md) |
 | `INVALID_ARGUMENT` / `NOT_ENOUGH_ASSETS` | Asset group below minimums | Add assets to meet the per-type counts in the table |
-| `INVALID_ARGUMENT` / `INVALID_ASSET_GROUP_ASSETS` | An asset is malformed or violates Google requirements | Fix the offending asset (length, type, url) |
+| `INVALID_ARGUMENT` / `INVALID_ASSET_GROUP_ASSETS` | An asset type's count is outside its range in the table, an asset type is unsupported, or an asset is malformed | Fix the count or the offending asset (length, type, url) |
 | `INVALID_ARGUMENT` / `INVALID_IMAGE_FORMAT` | Image format/dimensions unsupported | Use a supported ratio/size; regenerate via image-asset-suggestions |
 | `INVALID_ARGUMENT` / `DUPLICATE_IMAGE_ASSETS` / `DUPLICATE_ASSET` | Same asset provided twice | Deduplicate the asset group |
 | `INVALID_ARGUMENT` / `SEARCH_THEME_POLICY_VIOLATION` / `POLICY_VIOLATION` | A signal/asset violates Google policy | Remove or rewrite the flagged item |

package/skills/wix-manage/references/marketing/create-and-publish-social-post.md

@@ -1,40 +1,39 @@
 ---
-name: "Create and Publish a Social Media Post (with AI generation)"
-description: "End-to-end flow to create a social media post, optionally generating it with AI, and publish or schedule it to a site's connected channel (Instagram, Facebook, LinkedIn, X/Twitter, TikTok, Pinterest, YouTube, Google Business Profile) using the Wix Publisher API. Can generate a full per-channel post from a free-text idea or from the site's own assets (products, blog posts, events, bookings, coupons, categories), generate caption/title suggestions, and edit an existing image with AI. Settles the post content with you first, then confirms the channel is connected, checks premium quota, creates a draft, and publishes now or schedules it. Use for 'create a post', 'generate a post from my product/idea', 'write a caption', 'caption ideas/suggestions', 'edit a post image with AI', 'post to Instagram/Facebook/TikTok', 'connect my Instagram/Pinterest/LinkedIn', or 'schedule a post'."
+name: "Create and Publish a Social Media Post"
+description: "End-to-end flow to create a social media post, with its text written for you or your own, and publish or schedule it to a site's connected channel (Instagram, Facebook, LinkedIn, X/Twitter, TikTok, Pinterest, YouTube, Google Business Profile) using the Wix Publisher API. Can write a full per-channel post from a free-text idea or from the site's own assets (products, blog posts, events, bookings, coupons, categories), with your own image, and suggest captions and titles. Settles the post content with you first, then confirms the channel is connected, checks premium quota, creates a draft, and publishes now or schedules it. Use for 'create a post', 'generate a post from my product/idea', 'write a caption', 'caption ideas/suggestions', 'post to Instagram/Facebook/TikTok', 'connect my Instagram/Pinterest/LinkedIn', or 'schedule a post'."
 ---
-# RECIPE: Create and Publish a Social Media Post (with AI generation)
+# RECIPE: Create and Publish a Social Media Post
 
 ## THE PROTOCOL (read this first — every rule is mandatory)
 
 Run every post request through these steps, in this order. The principle is **value first**: settle *what the post is* and show it to the user before you touch delivery. Don't open with connection or plan checks — reach those only once there's an approved post to deliver. Skip a question only when the user's own words in this conversation already answered it.
 
 1. **Channel + subject first — no API calls yet.** Determine the target channel from the request; if the user didn't name one, ask. Then get, in the user's own words, what the post is **about**: a free-text idea, or a specific site asset (a product, blog post, event, booking, coupon, or category). The subject is a **hard gate** — a reply that answers only part of a question (an account pick, a bare "you decide") does not supply it, and you must never derive a topic from the site's profile or content on your own. Ask again and wait.
-2. **Ask: own or generated?** "Do you already have the post text (and image), or should I generate it?" Wait for the answer.
+2. **Ask: own or generated?** "Do you already have the post text, or should I write it? And which image goes with it: one of your site's, or one you upload?" The image is always the user's own. Wait for the answer.
 3. **If generating, ask: idea or asset?** "From an idea, or built around one of your site's assets (a product, blog post, event, booking, coupon, or category)?" Offer the asset option explicitly, every time. Wait for the answer.
 4. **Route exactly one way:**
    - User has their own text → use it **verbatim**; skip generation → go to STEP 3 (choose type), then STEP 6 (assemble).
-   - Idea → `generate-post-data` with `userInput` (STEP 2a; returns caption **and** image).
-   - Asset → resolve the asset id, then `generate-post-data` with `siteAssets` (STEP 2a).
+   - Idea → `generate-post-data` with `userInput` and the user's `media` (STEP 2a; returns the caption with that image).
+   - Asset → resolve the asset id, then `generate-post-data` with `siteAssets` and the asset's image as `media` (STEP 2a).
    - User explicitly wants **only** a caption → `generate-text` (STEP 2b).
-   - User wants an **existing image edited** → `generate-image` (STEP 2c; requires a source image URL).
 
-   To get an **AI image from a bare idea**, that's `generate-post-data` — it returns a generated image as part of the post. `generate-image` only *edits* an existing image (it returns 400 without a source image); there is no endpoint that turns a prompt into a standalone image.
+   No step produces an image. The post's image is the user's: a site asset's image, a file they upload, or a Media Manager file (**Media handling** in STEP 3).
 5. **Show it and get approval.** Present the tool's actual output — the caption **and** the image (rendered inline, or its URL). Never hand-write the caption or claim generated content you didn't get from the API. Get explicit approval on the final post **before** any delivery step.
-6. **Only now, check delivery — just-in-time.** After the user approves, confirm the channel is connected (STEP 4; connect if needed) and check the plan for publish vs. schedule (STEP 5). This is where connection/plan problems surface — never lead with them. If `SCHEDULE_POST` is disabled, never present scheduling. A positive `quotaInfo.limit` with `remainingUsage: 0` means that action's quota is used up (offer the other action if enabled — a near-future schedule works like publish-now); `limit: 0` means unmetered, so treat the action as available. AI generation is **never** plan-gated; never tell the user it is.
+6. **Only now, check delivery — just-in-time.** After the user approves, confirm the channel is connected (STEP 4; connect if needed) and check the plan for publish vs. schedule (STEP 5). This is where connection/plan problems surface — never lead with them. If `SCHEDULE_POST` is disabled, never present scheduling. A positive `quotaInfo.limit` with `remainingUsage: 0` means that action's quota is used up (offer the other action if enabled — a near-future schedule works like publish-now); `limit: 0` means unmetered, so treat the action as available. Generation is **never** plan-gated; never tell the user it is.
 7. **Publish exactly what was approved.** Create the draft (STEP 6) from the approved content plus the account's IDs, then publish or schedule (STEP 7). For a scheduled time, verify the resolved `scheduledDate` is **strictly in the future** right before the call (a "today at 9am"-style time can resolve to the past). Reuse the approved caption, image, and draft on any retry; never regenerate after approval.
 
 The rest of this recipe is the reference for executing each step.
 
 ---
 
-This recipe creates a post — called an **item** — and publishes it to one of a site's connected social channels, or schedules it for a future date. You can generate the post content with AI (STEP 2) or bring your own. Each item targets a single channel, and its `type` and content must match a combination the channel supports.
+This recipe creates a post — called an **item** — and publishes it to one of a site's connected social channels, or schedules it for a future date. You can have the post text written (STEP 2) or bring your own; the image is always the user's own. Each item targets a single channel, and its `type` and content must match a combination the channel supports.
 
 Base URL for all endpoints: `https://www.wixapis.com/social-publisher/v1`.
 
 **Prerequisites:**
 - AI generation (STEP 2) is available on every site — it is **not** plan-gated. Offer it by default; skip it only if the user brings their own caption and media.
 - To *deliver* the post, the target channel must be connected by the site owner (checked in STEP 4; connect it there if not) and the plan must allow the action (STEP 5).
-- Post media must be a **Wix Media Manager URL** (`static.wixstatic.com`); see **Media handling** in STEP 3. Images edited in STEP 2c are already hosted there.
+- Post media must be a **Wix Media Manager URL** (`static.wixstatic.com`); see **Media handling** in STEP 3.
 
 **Flow (value-first):** STEP 1 settle channel + subject → STEP 2 generate the content (offer this proactively) → STEP 3 choose channel/type → **show the post and get approval** → STEP 4 confirm the channel is connected (connect if needed) → STEP 5 check premium → STEP 6 create the draft → STEP 7 publish or schedule. Generation and approval come first so the user sees value before any connection or plan gate; the delivery checks (STEP 4–5) run just-in-time, right before creating and publishing.
 
@@ -53,9 +52,9 @@ Then follow THE PROTOCOL rules 2–4 to decide own-vs-generated and idea-vs-asse
 
 ---
 
-## STEP 2: Generate the post content with AI
+## STEP 2: Generate the post text
 
-AI generation isn't gated by the plan (no premium check applies), so offer it by default. **THE PROTOCOL at the top of this recipe governs this step**: hold the subject gate (rule 1), ask own-or-generated (rule 2), offer idea-or-asset (rule 3), and route per rule 4. Never hand-write the caption or title; producing the post means calling the API below and presenting *its* output.
+Generation isn't gated by the plan (no premium check applies), so offer it by default. **THE PROTOCOL at the top of this recipe governs this step**: hold the subject gate (rule 1), ask own-or-generated (rule 2), offer idea-or-asset (rule 3), and route per rule 4. Never hand-write the caption or title; producing the post means calling the API below and presenting *its* output.
 
 ### 2a. Generate a full post — from an idea and/or the site's own assets
 
@@ -75,12 +74,12 @@ Produces ready-to-use, per-channel payloads that drop into STEP 6. **This is the
   | `EVENT` | Wix Events | `POST https://www.wixapis.com/events/v3/events/query` (body `{ "query": { "paging": { "limit": 10 } } }` — `paging.limit` must be > 0) | [Query Events](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/query-events) |
   | `BOOKINGS_SERVICE` | Wix Bookings | `POST https://www.wixapis.com/bookings/v2/services/query` (body `{ "query": {} }`) | [Query Services](https://dev.wix.com/docs/api-reference/business-solutions/bookings/services/services-v2/query-services) |
 
-- `media` — candidate images to include, as `{ "type": "IMAGE", "url": "<public-url>" }` (images only).
+- `media` — the user's images to include, as `{ "type": "IMAGE", "url": "<public-url>" }` (images only). Always pass at least one: a site asset's image, an uploaded file, or a Media Manager file.
 - `channels` — which channels to generate for. Omit to get one result for each of `INSTAGRAM`, `FACEBOOK`, `LINKEDIN`, `PINTEREST`, `GBP`, and `TIKTOK`.
 
 Provide `userInput`, `siteAssets`, or both.
 
-**Scope:** this method produces standard image-**post** payloads for the six channels above only. It does **not** generate YouTube content, X/Twitter posts, or story/reel/video formats — for those, use 2b (caption) and 2c (image edit) and assemble the content object yourself in STEP 6.
+**Scope:** this method produces standard image-**post** payloads for the six channels above only. It does **not** generate YouTube content, X/Twitter posts, or story/reel/video formats — for those, use 2b (caption) and assemble the content object yourself in STEP 6.
 
 **Example — from an idea + an image, for Instagram and Facebook:**
 
@@ -117,7 +116,7 @@ Provide `userInput`, `siteAssets`, or both.
 }
 ```
 
-Use the payload for your chosen channel as the content object in STEP 6. When you pass no `media` of your own, `generate-post-data` returns an AI-generated image in `mediaWrapper.media[]` — review the **whole** payload with the user and surface that media, not just the caption (see STEP 3's approval note). The generated image's URL may live on a temporary external host rather than `static.wixstatic.com`; treat it like any external image — import it to the Media Manager (see **Media handling** in STEP 3) and use the imported URL in the post.
+Use the payload for your chosen channel as the content object in STEP 6. Pass the user's `media` on every call, so `mediaWrapper.media[]` holds their image; a result whose media is not the image you passed is not used. Review the **whole** payload with the user, the caption and the media (see STEP 3's approval note).
 
 ### 2b. Generate only a caption or title
 
@@ -139,33 +138,6 @@ Use when the user just wants caption suggestions to place into a post.
 
 **Expected response:** `{ "results": [ { "caption": "…", "title": "…" } ] }`. Put the chosen `caption` (and `title` where the channel uses one) into the content object in STEP 6.
 
-### 2c. Edit an image with AI
-
-Transforms an existing **source image** according to a text prompt (e.g. add a sale banner to a product photo, restyle a background). This is AI image-to-image editing — it requires a source image and does **not** generate an image from a prompt alone. Runs asynchronously.
-
-**API Endpoint:** `POST https://www.wixapis.com/social-publisher/v1/generate-image`
-
-Both `userInput` (prompt) and `imageUrl` (the source image to edit) are required:
-
-```json
-{
-  "userInput": "Add a bright summer-sale banner to the product photo",
-  "imageUrl": "https://static.wixstatic.com/media/cf2434_source-product-photo.jpg"
-}
-```
-
-**Response:** `{ "status": "OK", "executionId": "b7c2f0a1-4e6d-4a8b-9c3f-2d5e1a7b0c94" }`.
-
-**Poll** for the result: `GET https://www.wixapis.com/social-publisher/v1/generated-image/{executionId}` about every few seconds, for up to ~2 minutes, until `status` is `READY` or `FAILED`:
-
-```json
-{ "status": "READY", "imageUrl": "https://static.wixstatic.com/media/cf2434_generated-image.jpg", "fileId": "cf2434_abc123def456~mv2.jpg" }
-```
-
-`status` values: `IN_PROGRESS` (keep polling; if still `IN_PROGRESS` after ~2 minutes, stop and report), `READY` (use `imageUrl` — and `fileId` — as the post media), `FAILED`. A `404 GENERATED_IMAGE_NOT_FOUND` means the `executionId` is invalid or expired. The generated image is also saved to the site's "Social Marketing AI Media" Media Manager folder.
-
----
-
 ## STEP 3: Choose the channel and type (then show the post and get approval)
 
 For the target channel from STEP 1, pick the item `type` and the matching content object (from STEP 2's output or the user's own content).
@@ -188,11 +160,11 @@ For the target channel from STEP 1, pick the item `type` and the matching conten
 
 Notes:
 - Media items in `mediaWrapper.media[]` are `{ "type": "IMAGE" | "VIDEO", "url": "<public-url>" }`.
-- Instagram and story types **require** media (GBP needs `description` and/or media). There's no way to produce a standalone image from a prompt (2c only edits an existing image; 2a returns an image only *as part of* a generated post), so if the user has none and doesn't want a full 2a generation, source one — see **Media handling** below.
+- Instagram and story types **require** media (GBP needs `description` and/or media). The image is the user's own; if they have none at hand, take one of the site's assets or ask for an upload — see **Media handling** below.
 - `caption` is the text field for Instagram, Facebook, LinkedIn, and X/Twitter; `description` for YouTube, Pinterest, Google Business Profile, and TikTok.
 - The account-derived IDs (`pageId`, `boardId`, `locationId`, `authorId`, `channelId`, `privacyLevel`) come from the account object fetched in STEP 4b — see the field-path table there.
 - TikTok `privacyLevel` must be one of the account's `privacyLevelOptions` (from STEP 4b) — one of `PUBLIC_TO_EVERYONE`, `FOLLOWER_OF_CREATOR`, `MUTUAL_FOLLOW_FRIENDS`, `SELF_ONLY`.
-- Text length limits: Instagram `caption` ≤ 2200 (about 30 hashtags / 20 mentions); Pinterest `title` ≤ 100, `description` ≤ 800, `link` ≤ 2048; Google Business Profile `description` ≤ 1500; TikTok photo `title` ≤ 90 and `description` ≤ 4000, TikTok video `description` ≤ 2200. AI-generated captions/titles (STEP 2b) are ≤ 1000.
+- Text length limits: Instagram `caption` ≤ 2200 (about 30 hashtags / 20 mentions); Pinterest `title` ≤ 100, `description` ≤ 800, `link` ≤ 2048; Google Business Profile `description` ≤ 1500; TikTok photo `title` ≤ 90 and `description` ≤ 4000, TikTok video `description` ≤ 2200. Generated captions/titles (STEP 2b) are ≤ 1000.
 - GBP `callToAction` (optional) is one of `BOOK`, `ORDER`, `SHOP`, `LEARN_MORE`, `SIGN_UP`.
 - `TWITTER` (X) works like any other channel **only through July 31, 2026**; after that it's no longer functional (see STEP 7). Treat an `UNSUPPORTED_CHANNEL` error as authoritative.
 
@@ -201,8 +173,8 @@ Notes:
 **Media handling.** Post media **must be a Wix Media Manager URL** — `static.wixstatic.com` for images, `video.wixstatic.com` for videos. Always use one, even for media that came from elsewhere. (The API only validates a generic URL and won't reject a non-Wix link, but don't rely on that: an external URL has to stay reachable when the post publishes — a real risk for scheduled posts — and skips the Media Manager processing channels expect. Treat a Wix URL as required.) In the content object, `url` is that Wix URL; `fileId` is optional when `url` is supplied.
 
 Getting media into the Media Manager:
-- **Already there** (a site asset's image, a STEP 2c generated image, or a previously uploaded file) → use its `static.wixstatic.com` `url` directly.
-- **A public external URL** (including a 2a AI-generated image on a temp host) → import it; Wix fetches it server-side, no local download: `POST https://www.wixapis.com/site-media/v1/files/import` with `{ "url": "<external-url>", "mimeType": "image/jpeg", "displayName": "post.jpg" }`.
+- **Already there** (a site asset's image or a previously uploaded file) → use its `static.wixstatic.com` `url` directly.
+- **A public external URL** → import it; Wix fetches it server-side, no local download: `POST https://www.wixapis.com/site-media/v1/files/import` with `{ "url": "<external-url>", "mimeType": "image/jpeg", "displayName": "post.jpg" }`.
 - **A local file (no public URL)** → `POST https://www.wixapis.com/site-media/v1/files/generate-upload-url`, then **`PUT` the raw file bytes to the returned `uploadUrl`** (set `Content-Type` to the file's MIME type); the response returns the file descriptor. See the Media Manager Upload API.
 
 After import/upload the file returns `operationStatus: PENDING` — poll `GET https://www.wixapis.com/site-media/v1/files/{id}` until `operationStatus` is `READY`, then use its `static.wixstatic.com` `url` in the post.
@@ -487,14 +459,13 @@ The post appears on the site's Social Media Marketing page in the dashboard. To
 | `428 INELIGIBLE_FOR_FEATURE` on Get Connect Url | Site has hit its plan's cap on **number of connected channels** (e.g. free = 1), not a channel-specific block | Explain the channel-count limit; offer to upgrade, or find the already-connected channel (List Accounts / ask) and offer to post there. Don't suggest connecting a *different* new channel (same cap), don't suggest disconnecting/switching, don't retry the connect flow |
 | `FAILED_PRECONDITION` / `NO_PAGES_FOR_USER` on List Accounts | Connected Facebook/Instagram user has no page with a linked postable account | Ask the owner to grant a Facebook page (with a linked Instagram Business/Creator account) during authorization, then retry |
 | Publish fails on a missing account-derived ID (e.g. LinkedIn `/author :: field is required`) | The `authorId`/`pageId`/`boardId`/`locationId`/`channelId`/`privacyLevel` wasn't added to the content object | Read it from the STEP 4b account object per the field-path table and add it before publishing |
-| Generate Image poll returns `404 GENERATED_IMAGE_NOT_FOUND` | `executionId` invalid or expired | Re-run Generate Image and poll the new `executionId` |
 | STEP 5 shows the publish/schedule feature `enabled: false` or `remainingUsage: 0` | Plan doesn't allow the action, or quota used up | Advise upgrading, or wait for quota reset |
 | `FAILED_PRECONDITION` / `INELIGIBLE_FOR_FEATURE` on publish or schedule | Plan doesn't cover the action, or its quota is 0/exhausted (see the `quotaInfo` from STEP 5) | Don't retry; offer the other action if enabled (schedule vs publish now), or advise upgrading |
 | `SCHEDULED_TIME_ALREADY_PASSED` (or a generic/HTML `400`) on schedule | The resolved `scheduledDate` is in the past — usually a relative time like "today at 9am" that resolved to a past instant | Recompute the wall-clock time in the site's timezone, validate the ISO instant is `> Date.now()`, and advance to the next future occurrence (or confirm a later time) before retrying — don't send-and-catch |
 | `429 RESOURCE_EXHAUSTED` / `PUBLISH_LIMIT_EXCEEDED` | Publishing rate limit hit | Back off and retry later |
 | `ALREADY_EXISTS` / `REFERENCE_ID_ALREADY_EXIST` on create or publish | An item with the same `referenceId` already exists | Expected when safely retrying a create/publish that already succeeded — don't retry with a new `referenceId` |
 | `FAILED_PRECONDITION` / `UNSUPPORTED_CHANNEL` | Targeting an unsupported channel, or X/Twitter after its July 31, 2026 cutoff | Use a supported channel; target X only before the cutoff |
-| Create item rejected for missing media | Instagram and story types require media (GBP needs `description` and/or media) | Provide a public image/video URL (or edit one from a source image in STEP 2c) |
+| Create item rejected for missing media | Instagram and story types require media (GBP needs `description` and/or media) | Provide a public image/video URL from the user's own media |
 | Reschedule/cancel returns `ITEM_NOT_EXISTS`, `ITEM_IS_PUBLISHED`, or `ITEM_IS_DELETED` | The item can't be rescheduled/canceled in its current state | Only reschedule/cancel items still in `SCHEDULED` status |
 | Publish returns `status: FAILED` | Content/type mismatch or channel rejected the post | Verify the `type` + content object match the channel's supported combination and that media URLs are public |
 | An error arrives as an **HTML page** with only an HTTP status (no error code) | Some gateways render branded HTML error pages to non-browser callers, hiding the structured error | Interpret by status + endpoint: 428 on Get Connect Url = channel-count cap (handle per that row); 428 on publish/schedule = plan or quota gate. A 400 on `List Accounts` = channel not connected, but you shouldn't reach it — gate on `long-lived-token-status` (STEP 4a). Never read the page as "app not installed" or a random outage |
@@ -509,8 +480,6 @@ The post appears on the site's Social Media Marketing page in the dashboard. To
 - [Get Feature Data](https://dev.wix.com/docs/api-reference/business-management/marketing/social-media/premium-feature-v1/get-feature-data)
 - [Generate Post Data](https://dev.wix.com/docs/api-reference/business-management/marketing/social-media/generated-content-v1/generate-post-data)
 - [Generate Text](https://dev.wix.com/docs/api-reference/business-management/marketing/social-media/generated-content-v1/generate-text)
-- [Generate Image](https://dev.wix.com/docs/api-reference/business-management/marketing/social-media/generated-content-v1/generate-image)
-- [Get Generated Image](https://dev.wix.com/docs/api-reference/business-management/marketing/social-media/generated-content-v1/get-generated-image)
 - [Create Draft Item](https://dev.wix.com/docs/api-reference/business-management/marketing/social-media/item-v1/create-draft-item)
 - [Publish Item By ID](https://dev.wix.com/docs/api-reference/business-management/marketing/social-media/item-v1/publish-item-by-id)
 - [Reschedule Item](https://dev.wix.com/docs/api-reference/business-management/marketing/social-media/item-v1/reschedule-item)

package/skills/wix-manage/references/marketing/generate-and-publish-marketing-plan.md

@@ -1,6 +1,6 @@
 ---
 name: "Generate a Marketing Plan and Schedule Its Posts"
-description: "End-to-end flow to generate an AI-powered social media marketing plan for a site and schedule its generated posts for publishing, using the Wix Marketing Plan API. Recommends configuring marketing settings (goal, tone, cadence, content pillars) before the first generation, generates the plan asynchronously, polls until it's ready, then schedules the DRAFT posts. Includes generating posts for additional activities. Use for 'generate a marketing plan', 'create a social media plan/calendar', or 'schedule my plan's posts' requests."
+description: "End-to-end flow to generate a site's social media marketing plan with the Wix Marketing Plan API and schedule the post drafts it returns. Recommends configuring marketing settings (goal, tone, cadence, content pillars) before the first generation, generates the plan asynchronously, polls until it's ready, then schedules the DRAFT posts. Includes generating posts for additional activities. Use for 'generate a marketing plan', 'create a social media plan/calendar', or 'schedule my plan's posts' requests."
 ---
 # RECIPE: Generate a Marketing Plan and Schedule Its Posts
 
@@ -12,7 +12,7 @@ Walk every marketing-plan request through this conversation, in this order. Skip
 2. **Decide the settings with the user.** For each setting they want to change, use their words. If they want help choosing, fetch the selectable values (`GET .../marketing-settings/plan-goal-options`, `GET .../marketing-settings/defaults`) and propose suggestions for them to confirm. Write only values the user gave or confirmed; leave everything else to the site defaults. Never fabricate a goal, tone, or topic list on their behalf, and never put `language`, `targetLocations`, or `businessLocation` in the request or claim the call changed them.
 3. **Save, then offer to generate.** Upsert the confirmed settings (STEP 1, `fieldMask` as a comma-separated string matching exactly what you send), then offer to generate the plan — or, if a plan already exists, to regenerate it so the new settings take effect (settings are read only at generation time; use the keyword-research variant when `topics` changed). Poll until `ACTIVE` (STEPs 2-3).
 4. **Present the plan from the API data only.** Show the returned activities and their post drafts. Never invent activities, dates, or captions and present them as "the plan" — if it isn't in the response, it isn't in the plan (also applies to STEP 5's post generation).
-5. **Show before scheduling.** Scheduling publishes AI-generated drafts. Before Schedule Drafts (STEP 4), show each draft's caption and media (render the image inline, or give its URL) and get explicit approval. Schedule exactly what was approved — never regenerate after approval.
+5. **Show before scheduling.** Scheduling publishes the drafts the plan returned. Before Schedule Drafts (STEP 4), show each draft's caption and media (render the image inline, or give its URL) and get explicit approval. Schedule exactly what was approved — never regenerate after approval.
 6. **Diff the schedule response.** Only drafts for Publisher-connected channels are scheduled; the rest silently stay `DRAFT`. Compare the returned `SCHEDULED` ids against the ids you sent, and tell the user which drafts didn't schedule and which channel needs connecting (STEP 4).
 7. **Respect cutoffs and gates.** Skip `TWITTER` drafts dated after July 31, 2026. `FAILED_PRECONDITION` on Schedule Drafts means the plan lacks the premium scheduling feature: say so once and stop; it is not a transient error to retry.
 
@@ -20,7 +20,7 @@ The rest of this recipe is the reference for executing each step.
 
 ---
 
-This recipe generates a site's AI marketing plan — a schedule of marketing activities (social campaigns, blog posts, emails) from today through the end of next month — and schedules the social posts it generates. Generation is **asynchronous and non-deterministic**: you fire it, poll until it's ready, then act on the results.
+This recipe generates a site's marketing plan — a schedule of marketing activities (social campaigns, blog posts, emails) from today through the end of next month — and schedules the social posts it generates. Generation is **asynchronous and non-deterministic**: you fire it, poll until it's ready, then act on the results.
 
 Base URL for all endpoints: `https://www.wixapis.com/promote/marketing-plan-service/v1`.
 
@@ -143,7 +143,7 @@ Posts are generated automatically only for the **near-term** activities (how far
 
 ## STEP 4: Schedule the draft posts
 
-Collect the `id` of every `item` whose `status` is `DRAFT` from the activities you want to publish. **Before scheduling, show the user what will be published** — each draft's caption and media (render the image inline if the surface supports it, otherwise post its URL as a clickable link) — and get their approval. The drafts are AI-generated and scheduling publishes them, so never schedule content the user hasn't reviewed. Skip `TWITTER` drafts whose activity date falls after **July 31, 2026** — X is sunset then, and a post scheduled past the cutoff will never publish.
+Collect the `id` of every `item` whose `status` is `DRAFT` from the activities you want to publish. **Before scheduling, show the user what will be published** — each draft's caption and media (render the image inline if the surface supports it, otherwise post its URL as a clickable link) — and get their approval. The drafts are the plan's words, not the user's, and scheduling publishes them, so never schedule content the user hasn't reviewed. Skip `TWITTER` drafts whose activity date falls after **July 31, 2026** — X is sunset then, and a post scheduled past the cutoff will never publish.
 
 **API Endpoint:** `POST https://www.wixapis.com/promote/marketing-plan-service/v1/marketing-plan/schedule-drafts`