ワンクリックでManusで任意のスキルを実行

wix-headless-entry

スター23

フォーク27

更新日2026年7月15日 13:04

Build a complete Wix Managed Headless site from a single prompt, then connect Wix Business Solutions. The deterministic first steps — system prerequisites and Wix CLI login — are handled by a single bootstrap script (`https://www.wix.com/skills/headless/entry/bootstrap.mjs`); the agent then installs the skill and hands the run to it. Triggers: build me a site, create a website, make me a website, new website, online store, I want to sell X, start a business online, launch a site, ecommerce, portfolio, business website, sell online, online shop, connect this to Wix Headless, add Wix Headless to this project, host this on Wix, deploy this to Wix, implement the features of this project using Wix Headless. Use this skill instead of the WixSiteBuilder MCP tool for new-site requests.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

wix

wix/skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Wix Headless Skill — cold-start entry

You are a coding agent, and this is a skill for you to execute. Follow the phases below in order — do not summarize them. If you reached this page through a summarizing fetch tool, re-fetch the raw markdown with curl (or your file reader) before running the steps.

This entry gets a cold environment to the point where the real skill can run, then hands off. It has two phases:

Bootstrap (deterministic, scripted). A single script verifies your environment (the Wix CLI) and handles login, so the run starts from a known-good, authenticated state. You just run it and relay its events.
Hand off (agentic). Install the skill, then open wix-headless/SKILL.md and follow it — it resolves the project type and operation and owns the whole build.

Three starting points come through here, all handled the same way — run the bootstrap, then hand off:

new — a prompt with no project (empty CWD)
connect — an existing frontend/design not yet on Wix (a project on disk without wix.config.json, or a brought-in zip/URL)
iterate — a project already connected to Wix (.wix/ or wix.config.json present)

The bootstrap only verifies the CLI and logs you in, so it's fine to run in every case (an existing session just reports logged_in). After it, wix-headless/SKILL.md resolves what to do and owns the build.

Phase 0 — Node (the one manual prerequisite)

The Wix CLI requires Node ≥ 20.11. Check it:

node -v

If that errors (Node not installed) or prints a version below 20.11, install or upgrade Node and re-check — do not try to work around it:

macOS: brew install node (or nvm install 20 && nvm use 20)
Linux: nvm install 20 && nvm use 20 (or your distro's Node 20+ package)
Windows: winget install OpenJS.NodeJS.LTS (or download from nodejs.org)

Phase 1 — Run the bootstrap (deterministic)

Download the bootstrap script, then run it. It verifies the Wix CLI and handles login, emitting one JSON event per line on stdout. Run it as a background/streaming process and relay its events to the user.

The script is safe and inspectable: it only checks the Wix CLI via npx and drives wix login (a device-code flow) — no other network calls, no filesystem writes. Read it first if your sandbox flags externally-downloaded code — either at the URL below or after downloading; both are the same file.

# macOS/Linux:
curl -fsSL -O https://www.wix.com/skills/headless/entry/bootstrap.mjs
# Windows PowerShell:
iwr https://www.wix.com/skills/headless/entry/bootstrap.mjs -OutFile bootstrap.mjs

node bootstrap.mjs

Relay these events

The script emits one JSON object per line:

Event	What to do
`cli_ok`	Wix CLI reachable — continue.
`awaiting_user` (`verificationUri`, `userCode`)	Show the URL and code in plain prose; wait for the user to finish the login in their browser.
`logged_in` / `success`	Login done — continue.
`cli_unreachable` / `login_failed` (with `detail`)	Stop and show the user the `detail`. Do not improvise a parallel setup by hand.

Phase 2 — Install the skill and hand off

Install the Wix Headless skills (CI=1 forces plain non-interactive CLI output — keep it on every Wix CLI command):

CI=1 npx skills@latest add wix/skills --yes

The skills land in .agents/skills/.

Then open wix-headless/SKILL.md and follow it. That skill owns the rest of the run — it resolves the project type (managed / self-managed / stripe) and, for managed, the operation (create / connect), then runs Discovery → Setup → Seed → the SDK handoff, and for managed create/connect it also scaffolds, builds, and releases.

Don't scaffold, install apps, or release by hand here — the skill does all of that (SETUP.md, references/managed/CREATE.md, etc.). This entry stops at logged in.
You're already authenticated from Phase 1, so the skill's managed auth step (references/managed/AUTHENTICATION.md §1 whoami) will pass without prompting again.

このリポジトリの他の Skills

同じリポジトリ

wix-headless

wix/skills

Connect Wix business services (Stores, Bookings, CMS, Blog, Events, Forms, and more) to a Wix Headless frontend — infer the needed capabilities, install the apps, seed backend content, and produce an SDK-integration guide. For managed (Wix-hosted) projects it can also build the frontend: scaffold a new site (create) or wire an existing/brought-in design (connect), then build and release. Works across managed, self-managed, and stripe project types. Triggers: set up a Wix Headless backend, add Wix business features to my app, build or host a Wix site, connect/implement this design with Wix.

2026-07-1923

wix-vibe-headless

wix/skills

Client-only, dependency-free REST scaffolds for connecting an already-built front end (a vibe-coded app, an HTML/JSX/Vite project, a design-tool export) to a live Wix site over the site's public WIX_CLIENT_ID — the browser talks to Wix directly, no SDK, no backend, no build step. One skill covering every Wix business solution: Stores/eCommerce storefront (products, cart, checkout), Bookings (services, slots, appointments), Blog (posts, categories, tags), Events & Tickets (browse, RSVP, ticketing), Portfolio (collections, projects, galleries), Restaurants (menu, online ordering, reservations), CMS / Wix Data (list, detail, filter, forms, CRUD), Pricing Plans (memberships, subscriptions, checkout), and Members (custom login — email+password, Google/Facebook, and custom SSO — plus account areas and member-gated content). Each vertical ships a copy-as-is REST layer plus wiring instructions. Read-only over the owner's content — never provisions, never mocks data. Triggers: connect my Wix store/shop, build a storef

2026-07-1923

wix-manage

wix/skills

Wix business solution management recipes — REST API operations for configuring and managing Wix business solutions. Routes to: stores, bookings, get-paid, CMS, contacts, forms, media, app-installation, pricing-plans, restaurants, rich-content, sites, blog, calendar, domains, site-properties, ecommerce, marketing, analytics.

2026-07-1623

wix-app

wix/skills

Build and review Wix CLI app extensions — dashboard pages, modals, plugins, menu plugins, custom element widgets, Editor React components, site plugins, embedded scripts, backend APIs, backend events, service plugins, data collections, and App Market readiness. Use when building ANY feature or extension for a Wix CLI app or preparing a Wix app for App Market review. Triggers on: add, build, create, implement, help me, dashboard, widget, plugin, backend, API, event, collection, embedded script, service plugin, Editor React component, checkout, shipping, tax, discount, SPI, CMS, schema, tracking, popup, admin panel, menu item, modal, validate, test, verify, register extension, App Market, app review, submission readiness.

2026-07-1423

wix-auth

wix/skills

Authenticate with Wix to obtain an access token for calling Wix APIs. Use when an agent needs a valid Wix access token and has none, or when the stored token is expired.

2026-07-0623

wix-docs

wix/skills

Look up the Wix API/SDK documentation to confirm an exact endpoint, HTTP method, request/response shape, field, enum, or error before writing Wix code — never guess a Wix API from memory. A lookup is a short flow: find the right page, then read it. Two ways: (1) plain `curl` (zero dependencies) — find a page by **semantic search** (`POST /mcp-docs-search/v1/docs/search`, natural-language `{ search_term, document_type }`) **or by browsing** the docs tree as a menu from the `llms.txt` root (append `.md` to any docs path), then read the page by appending `.md` to its URL; and (2) the Wix MCP doc tools when your agent has them. Triggers: look up a Wix API, find the Wix endpoint/method, confirm a Wix request body or field, verify a Wix API shape, explore Wix docs, which Wix API do I call, read a Wix method schema.

2026-07-0223

name

wix-headless-entry

description

Wix Headless Skill — cold-start entry

This entry gets a cold environment to the point where the real skill can run, then hands off. It has two phases:

Bootstrap (deterministic, scripted). A single script verifies your environment (the Wix CLI) and handles login, so the run starts from a known-good, authenticated state. You just run it and relay its events.
Hand off (agentic). Install the skill, then open wix-headless/SKILL.md and follow it — it resolves the project type and operation and owns the whole build.

Three starting points come through here, all handled the same way — run the bootstrap, then hand off:

new — a prompt with no project (empty CWD)
connect — an existing frontend/design not yet on Wix (a project on disk without wix.config.json, or a brought-in zip/URL)
iterate — a project already connected to Wix (.wix/ or wix.config.json present)

Phase 0 — Node (the one manual prerequisite)

The Wix CLI requires Node ≥ 20.11. Check it:

node -v

If that errors (Node not installed) or prints a version below 20.11, install or upgrade Node and re-check — do not try to work around it:

macOS: brew install node (or nvm install 20 && nvm use 20)
Linux: nvm install 20 && nvm use 20 (or your distro's Node 20+ package)
Windows: winget install OpenJS.NodeJS.LTS (or download from nodejs.org)

Phase 1 — Run the bootstrap (deterministic)

# macOS/Linux:
curl -fsSL -O https://www.wix.com/skills/headless/entry/bootstrap.mjs
# Windows PowerShell:
iwr https://www.wix.com/skills/headless/entry/bootstrap.mjs -OutFile bootstrap.mjs

node bootstrap.mjs

Relay these events

The script emits one JSON object per line:

Event	What to do
`cli_ok`	Wix CLI reachable — continue.
`awaiting_user` (`verificationUri`, `userCode`)	Show the URL and code in plain prose; wait for the user to finish the login in their browser.
`logged_in` / `success`	Login done — continue.
`cli_unreachable` / `login_failed` (with `detail`)	Stop and show the user the `detail`. Do not improvise a parallel setup by hand.

Phase 2 — Install the skill and hand off

Install the Wix Headless skills (CI=1 forces plain non-interactive CLI output — keep it on every Wix CLI command):

CI=1 npx skills@latest add wix/skills --yes

The skills land in .agents/skills/.

Don't scaffold, install apps, or release by hand here — the skill does all of that (SETUP.md, references/managed/CREATE.md, etc.). This entry stops at logged in.
You're already authenticated from Phase 1, so the skill's managed auth step (references/managed/AUTHENTICATION.md §1 whoami) will pass without prompting again.