Index of every page on this site: llms.txt
All skills
wix avatar

/wix-manage

@e2bc48e official
by Wix.comwix/skills40 stars
42
Run it yourself

REST recipes to configure and manage a Wix site's business solutions — stores, bookings, donations, payments, CMS, and more — and to publish HTML, CSS and JavaScript files as a live Wix site, with or without a Wix account. Open the matching recipe for the exact endpoint, method, and payload before calling — never guess a Wix API, never write Wix dashboard URL from memory. Routes to: automations, stores, bookings, donations, get-paid, CMS, contacts, forms, media, app-installation, custom-apps, pricing-plans, restaurants, ricos rich-content, sites, collaborators, studio-workspace, blog, calendar, domains, events, site-properties, ecommerce, marketing, online-programs, google-ads, google-business-profile, analytics, accessibility, seo, dashboard-navigation.

Use this Skill: https://skilld.dev/gh/wix/skills/wix-manage

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencessitessend-feedback-to-wix.md

≈1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Send Feedback to Wix

Feedback reaches the Wix teams that own the APIs, docs, recipes and tooling. It is about the experience of building with Wix, not the user's site content, and it is not support.

When to offer it

Sending is the user's call; offering is yours. Offer once per issue, in plain prose, and send only after the user says yes.

  • The user asks to tell Wix something. Confirm the wording, then send.
  • The user is frustrated with Wix, or reports a Wix bug. Acknowledge it, then offer.
  • The run hit friction: a call that failed or needed retries, an error that didn't explain itself, a doc or recipe that was wrong, missing or ambiguous, a workaround you had to invent, a flow that fell back to a worse route.
  • At the end of a run that hit any of these, even ones you recovered from.

When you offer, invite the user to add their own words. Never send without a yes, never twice for the same issue, and never for a single transient error.

Compose the message

Wix receives free text. A bare sentence can't be triaged, so send a summary of the whole run in four parts.

Provenance, as labeled lines; drop the ones that don't apply:

Agent / model: <the agent and model you are>
Wix tooling: <Wix MCP, Wix CLI, REST from a shell, ...>
Recipes: <the recipes this run followed>
Wix products and APIs: <Stores, headless drop, the upload tool, ...>
Site: <metaSiteId> · dashboard: <url> · live: <url>
Other ids: <request ids, upload ids, execution ids>

Narrative:

  • In the user's words: what they added, verbatim. Skip when empty.
  • What the user set out to do, and how the run went: what worked and what fought back.
  • A condensed play-by-play: the key calls, what came back, and the decisions you made. Distilled, not a transcript.

Friction points, the heart of it. For each: the step or endpoint, the HTTP status and error text, the request id, what you expected, and what you did instead. Add your best guess at where the fault lives, from API behavior, API schema, API docs, docs articles or examples, a recipe, the Wix MCP, Wix tooling, or unsure, and say whether you confirmed it. "Unsure" beats a wrong guess.

Bottom line: one or two sentences naming the most important problem and its impact.

Show the user the final wording before sending. Leave out tokens, API keys and credentials, and any personal data the feedback doesn't need.

Send it

The call identifies the user, so it takes a user identity: a token from npx @wix/cli@latest token, or account scope in a script. A site-scoped token is refused as anonymous.

curl -sS -X POST "https://www.wixapis.com/mcp-serverless/v1/headless-feedback" \
  -H "Authorization: Bearer $ACCESS_TOKEN" -H 'Content-Type: application/json' \
  -d '{"message":"<the composed message>"}'

In an ExecuteWixAPI script, with the message as one text file in the files param:

async function run() {
  return await wix.request({ scope: 'account', method: 'POST',
    url: 'https://www.wixapis.com/mcp-serverless/v1/headless-feedback',
    body: { message: files[0].content } });
}
Response Meaning
200 with {} Sent. Tell the user.
500 "Unable to determine target user id, anonymous messages are not allowed" The token was site-scoped. Get a user token and send once more.
401 or 403 The CLI login expired. Run npx @wix/cli@latest login, get a new token, and send once more. If it fails again, show the user the response.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alerttoday4 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The skill is a comprehensive management tool for Wix sites. It contains potential security risks such as an indirect prompt injection surface from site scraping and the ability to define JavaScript-based automation logic, but it includes strong requirements for user confirmation before any site changes.

  • Sockettoday

    No alerts

  • Snyk1d

    Risk: CRITICAL · 3 issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at e2bc48e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 days ago
compatibility
Requires Wix REST API access (API key or OAuth).
  • wix
  • rest-api
  • ecommerce
  • bookings
  • cms
  • contacts
  • blog
  • domains
  • restaurants
  • site-configuration
  • api-integration

README badge

README badge for wix/skills/wix-manage

REST API operations for configuring Wix business solutions including stores, bookings, CMS, contacts, domains, and ecommerce. Routes to site setup, entity management (products, services, staff), bulk administrative operations, and server-to-server integrations across Wix's business app ecosystem.

Generated from the current SKILL.md.

Do I need API credentials to use these recipes?
Yes. The skill requires Wix REST API access via either an API key or OAuth token to execute any management operations.
Can I use these recipes to display data on my site frontend?
No. These recipes are for backend REST API operations only — site configuration, entity management, and administrative tasks. They do not cover frontend development or displaying data to users.
What business domains do these recipes cover?
The skill covers stores, bookings, payments, CMS, contacts, forms, media, apps, pricing plans, restaurants, rich content, sites, blogs, calendars, domains, and site properties.
Do these recipes handle OAuth authentication with external services like Google Calendar?
Yes. The external calendar integration recipe covers OAuth-based setup with Google Calendar, Microsoft Outlook, and Apple Calendar for bidirectional event sync.

Generated from the current SKILL.md. These answers refresh after source changes.