wix-cli-orchestrator

Orchestrates Wix CLI extension selection, implementation sub-agents, and validation workflows.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/ESSSoWhat/live-translate-realtime-dubbing --skill wix-cli-orchestrator-esssowhat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wix-cli-orchestrator
Source: https://github.com/ESSSoWhat/live-translate-realtime-dubbing/tree/main/wix-app/np/.agents/skills/wix-cli-orchestrator
Command: npx skills add https://github.com/ESSSoWhat/live-translate-realtime-dubbing --skill wix-cli-orchestrator-esssowhat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building features for a Wix CLI app requires choosing among many extension types (dashboard pages, modals, plugins, service plugins, data collections, site widgets) and coordinating SDK discovery, implementation, and validation. This Skill removes that guesswork by acting as a decision-maker and orchestrator that routes every Wix feature request through a mandatory, checklist-driven workflow. ## Core Features & Use Cases - Extension Type Selection: Decision tables and flowcharts map requirements (admin UI, backend logic, data storage, site components) to the correct Wix CLI extension type and its corresponding implementation skill. - Sub-Agent Orchestration: Spawns discovery sub-agents for SDK methods not covered in reference files, then spawns implementation sub-agents in parallel with full context, and finishes with mandatory validation via the wix-cli-app-validation skill. - Data Collection Inference: Automatically detects when app data persistence implies a Data Collection extension, coordinates app namespace and scoped collection IDs across sub-agents. - Use Case: A user asks to "add a dashboard page to manage shipping fees that apply at checkout." The Skill infers a Dashboard Page plus a Service Plugin plus a Data Collection, obtains the app namespace, spawns parallel implementation sub-agents with scoped collection IDs, runs validation, and surfaces all manual setup steps. ## Quick Start Ask the assistant to build a Wix app feature, for example: add a dashboard page that manages product recommendation rules stored in a collection.

Frequently Asked Questions about wix-cli-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Wix CLI extension type for my feature?

Match your requirement to the decision flow: admin interfaces map to Dashboard Pages, Modals, or Plugins; backend logic maps to Service Plugins, Event Extensions, or HTTP Endpoints; data storage maps to Data Collections; and site-facing UI maps to Site Widgets, Components, or Plugins.

How do I add a dashboard page to a Wix CLI app?

The orchestrator recommends a Dashboard Page extension, checks reference files for needed APIs like the Dashboard SDK or Wix Data, then spawns an implementation sub-agent using the wix-cli-dashboard-page skill. Validation runs afterward to confirm the build and preview succeed.

When is a Data Collection extension required in a Wix app?

A Data Collection extension is required whenever the app stores or manages its own data, such as dashboard CRUD pages or service plugins reading app-configured rules. It requires an app namespace from the Wix Dev Center, and collection IDs are scoped as namespace/idSuffix.

What is the difference between a Wix site widget, site component, and site plugin?

A site widget is a standalone component users place anywhere, a site component is a React component with an editor manifest for styling and content, and a site plugin occupies a fixed slot in a Wix business solution page. Only site components can consume context provider extensions.

Does the orchestrator write Wix extension code itself?

No. The orchestrator only decides, discovers, and delegates. It spawns implementation sub-agents with the appropriate extension skill, user requirements, and SDK context, then runs the wix-cli-app-validation skill before reporting completion.

Why must Wix Stores APIs check the catalog version first?

Wix Stores has incompatible V1 and V3 catalogs, so all Stores operations must call getCatalogVersion() and use productsV3 for V3 or products for V1. The orchestrator enforces this by including the wix-stores-versioning skill in any sub-agent using Stores APIs.