wix-manage

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.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/wix/skills/wix-manage/SKILL.md

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-architected recipe index with excellent progressive disclosure and a lean, non-padded structure. Its weaker spots are body-level actionability and workflow clarity, since executable code and validation checkpoints largely live in the referenced files rather than the index itself.

Suggestions

Surface one or two inline validation checkpoints for the batch/destructive recipes (e.g., a dry-run/count check before 'Bulk Delete Contacts') to raise workflow clarity.

Add a short shared 'verify the call succeeded' snippet near the top auth note so the body carries at least one complete executable pattern, not just pointers.

Dimension	Reasoning	Score
Conciseness	The body is a lean index: each recipe is a link plus a single dense 'Technical:' line, with no padding explaining Wix or basic concepts; the shared auth note and ecommerce routing block are functional rather than filler, so every token earns its place.	3 / 3
Actionability	The body offers one concrete copy-paste command ('npx @wix/cli@latest token --site "$SITE_ID"') and concrete header/routing rules, but most entries describe-and-link rather than providing executable code, deferring the bulk of instruction to reference files.	2 / 3
Workflow Clarity	Categorical organization and the ecommerce decision tree give a clear routing sequence, but the body contains no validation checkpoints or feedback loops, and batch/destructive recipes (bulk delete contacts, bulk create products) show no inline verification, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	SKILL.md is a clear overview pointing to 69 verified reference files exactly one level deep (references/<category>/<file>.md), with well-signaled links, category navigation, and internal-only skills collapsed in a <details> block — matching the 'clear overview with one-level-deep references' anchor.	3 / 3
	Total	10 / 12 Passed

Description

82%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly names its Wix REST API niche and enumerates concrete capability areas with natural trigger terms. Its main gap is the absence of an explicit 'Use when...' trigger clause, leaving the 'when' only implied.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when configuring or managing Wix business entities via the REST API') to convert the implied routing into an explicit trigger and lift completeness.

Consider leading with the trigger condition before the route list so the 'when' is unambiguous at a glance.

Dimension	Reasoning	Score
Specificity	Names the domain (Wix business solutions, REST API) and enumerates many concrete capability areas — 'stores, bookings, get-paid, CMS, contacts, forms, media...' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	'What' is answered explicitly ('REST API operations for configuring and managing Wix business solutions'), but 'when' is only implied via the 'Routes to:' list rather than an explicit 'Use when...' clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	The route list surfaces natural terms a Wix site owner would say ('stores', 'bookings', 'pricing plans', 'restaurants', 'blog', 'domains'), giving good coverage of common user phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped to Wix REST API management with a distinct enumerated niche, making it unlikely to trigger for unrelated skills; the route list provides distinct triggers.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 76 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 76 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: openai/plugins
Path: plugins/wix/skills/wix-manage/SKILL.md
Commit: 11c74d6

Reviewed: ~1 month ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.