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.

referencesdomainscheck-domain-availability.md

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

Check Domain Availability

Answers one question: can this domain be registered? and ends with an offer for the next step. It never buys, connects, searches for alternatives or prices a domain itself: the offer is only a question. Every availability lookup goes through this skill, including the ones inside Connect Domain, Purchase Domain, Assign Domain and Connect External Domain or Sub Domain: those skills run the check and read the results as written here, and add their own next steps and wording.

Which check to run: when you have a domain-availability tool — one that takes a list of domain names and returns a status for each — use it (§With an availability tool). Use the endpoints (§Single check, §Bulk check) only when there is no such tool, and for the one follow-up that section names. Both endpoints are public: send the request without auth headers or tokens.

Flow

  1. Normalize each domain: lowercase, trim whitespace, strip http://, https://, www. and any path. Keep the extension the user typed.
    • No extension (mybakery), asked about on its own: ask which extension they want, or offer suggestions through Purchase Domain. Do not guess one. Inside a list, keep it in the bulk call: the item comes back as INVALID_DOMAIN.
    • Subdomain (shop.example.com): do not check it — a subdomain is not registered separately. Check the root domain (example.com) only if the user asks about that.
  2. One call for every name: one availability-tool call with all of them. Without such a tool: one domain → single check; two or more → one bulk check, never one single check per domain.
  3. Read the result per domain, answer in plain language and end with the offer (table below).
  4. Run the check silently — no "let me check". Retry any failed call once, silently. If it fails again: a 400 means the input is bad (see the table below and the 60-domain limit); anything else, say "Something went wrong on our end. Please try again in a moment."

Never name an endpoint, a field or an error code to the user.

With an availability tool

One call, every name in the list, in the order the user gave them. The shape seen today:

{ "domains": ["example.com", "4321.online", "-bad-.com"] }
{ "results": [ { "domain": "example.com", "status": "AVAILABLE" },
               { "domain": "4321.online", "status": "PREMIUM" },
               { "domain": "-bad-.com",   "status": "UNABLE_TO_CHECK" } ] }

Read status for every result:

status Read it as
AVAILABLE the available: true row below
PREMIUM the premium: true row below
UNABLE_TO_CHECK, or any other status The status does not say why (a malformed name such as -bad-.com gets UNABLE_TO_CHECK). Run the single check below once for that name and read its result in the table. If that call fails too, say "I couldn't check {domain} right now."

One follow-up single check per name the tool could not read. Answer every name in one reply, in the order the user gave them.

Either path ends in the endpoint fields: AVAILABLE is available: true, PREMIUM is premium: true, and any other status takes the single check's own result. A skill that reads available and premium reads them the same way, whichever check ran.

Single check

GET https://www.wixapis.com/domain-search/v2/check-domain-availability?domain=example.com
{ "availability": { "domain": "example.com", "available": true, "premium": false,
                    "premiumType": "UNKNOWN_PREMIUM_TYPE" } }

Bulk check

Up to 60 domains per call. A larger list is rejected with 400; split it into batches of 60.

POST https://www.wixapis.com/domain-search/v2/bulk/domain-availabilities/check
Content-Type: application/json

{ "domains": ["example.com", "myshop.ws"] }
{ "results": [
    { "itemMetadata": { "id": "example.com", "originalIndex": 0, "success": true },
      "item": { "domain": "example.com", "available": true, "premium": false,
                "premiumType": "UNKNOWN_PREMIUM_TYPE" } },
    { "itemMetadata": { "id": "myshop.ws", "originalIndex": 1, "success": false,
                        "error": { "code": "TLD_NOT_SUPPORTED", "description": "Unsupported tlds" } } } ],
  "bulkActionMetadata": { "totalSuccesses": 1, "totalFailures": 1 } }

The call returns 200 even when some items fail. Check itemMetadata.success on every result; a failed item has error and no item.

A name that is not a well-formed hostname, such as -bad-.com, is not an item error: it fails the whole request with 400, naming it as domains[i] (the position in your list). Keep that name aside to report as invalid, resend the list without it, and answer for every name in one list, the invalid one included, in the order the user gave them.

Reading the result

Result Say Then offer
available: true "{domain} is available." "Would you like to get it for your Wix site?"
premium: true (with available true or false) "{domain} is available as a premium domain — it costs more than a standard one." Do not give a price figure. "Would you like to get it for your Wix site?"
available: false, premium: false "{domain} is already registered." Nothing more about it. "If it's yours, I can connect it to your Wix site. Or I can look for similar names that are available."
Single check: 400 with details.applicationError.code = DOMAINS_UNSUPPORTED_TLD; bulk item error TLD_NOT_SUPPORTED "We don't currently support .{extension} domains." "Want me to look for similar names with a supported extension?"
Bulk item error INVALID_DOMAIN; bulk request 400 naming domains[i]; single check 400 with details.validationError "{input} isn't a valid domain name." Ask for a corrected one. For the bulk 400, the other names are still checked (see above). The request for a corrected name is the only follow-up.

One offer per reply. For a single domain, add the offer from its row after the answer. For several domains, answer one line each, then close with one offer that covers only the kinds present, for example: "Want to get any of the available ones, connect one that's yours, or see similar names?"

  • The response has no price. Never state or estimate a price figure, for any result.
  • premium: true marks a premium domain: it can be registered, at a higher price than a standard domain. The API may report such a domain as available: false; read premium first. It is a pricing tier of the domain, not the Wix Premium plan of a site.
  • premiumType is always UNKNOWN_PREMIUM_TYPE today; ignore it.
  • For several domains, answer in one list or table, one line per domain, in the order the user gave them.

Boundaries

A taken or premium domain gets the answer and offer above and nothing else: no owner, registrar, WHOIS lookup, valuation or price. The offer is a question. Do not run an ownership lookup, a suggestions search, a purchase or a connection to make it, and do not ask "do you own it?" beyond the offer's wording.

Next step

Only after the user answers the offer: buy a domain, or look for similar names → Purchase Domain (it also holds the suggestions step); connect one they own → Connect Domain. Inside those flows they decide the reply and the table above does not apply.

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.