Name: wix
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

wix

Wix integration. Manage Stores. Use when the user wants to interact with Wix data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/wix/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

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

The body is a strong, actionable integration guide with concrete CLI commands, a polling-based connection workflow, and well-organized sections. Its main weaknesses are mild verbosity in the intro/marketing phrasing and loose step numbering plus missing validation guidance for destructive action runs.

Suggestions

Trim the opening paragraph explaining what WIX eCommerce is and remove marketing phrasing like 'so you can focus on the integration logic' to tighten conciseness.

Reconcile the workflow numbering (the text references 'Step 1'/'Step 2' and '1b' without matching headers) into a single consistent numbered sequence.

Add a brief validation/review step before running destructive or batch actions (e.g., confirm object IDs and dry-run list before delete-product or update-order) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it opens with an unnecessary explanation of what WIX eCommerce is and includes marketing-flavored padding ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens'), fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than the lean score-4 anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for every phase (login, connection ensure, action list/run, request) plus a Popular actions table, but some examples rely on placeholders (CONNECTION_ID, <actionId>) and the empty-URL `membrane connection ensure ""` is unusual, leaving minor gaps short of the fully-executable score-5 anchor.	4 / 5
Workflow Clarity	The connect-and-poll workflow has a clear sequence with a real feedback loop (poll BUILDING, handle CLIENT_ACTION_REQUIRED, re-poll) and error-state handling, but the 'Step 1 / Step 2 / 1b' numbering is loose and there is no validation checkpoint after running destructive actions (delete-product, update-order), so it stops short of the score-5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist, so the score reflects the single-file structure: clear section headers and a logical overview-to-detail flow with only minor organization gaps (the Popular actions table and full proxy-options list are inline but reasonable), matching the 'good structure; most content appropriately placed' anchor rather than the multi-file score-5 anchor.	4 / 5
	Total	15 / 20 Passed

Description

57%Weight 40%Scale 1-5

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

The description cleanly provides a 'when' trigger and a distinct Wix niche, but its 'what' is generic ('Manage Stores') and lacks concrete capabilities or richer trigger synonyms. Tightening the action list and adding terms like products, orders, and eCommerce would lift specificity and trigger quality.

Suggestions

Replace the generic 'Manage Stores' with 2-3 concrete actions (e.g., 'Manage products, orders, collections, and inventory in your Wix store') to raise specificity.

Add natural trigger synonyms users would say, such as 'Wix store', 'Wix eCommerce', 'products', or 'orders', to improve trigger term coverage.

Make the 'when' clause more concrete by tying it to specific tasks (e.g., 'Use when the user wants to query or update Wix store products, orders, or inventory').

Dimension	Reasoning	Score
Specificity	The description names the domain ('Wix integration') and one action ('Manage Stores'), but that action is generic rather than concrete, matching the 'names the domain but actions are minimal or generic' anchor rather than the multi-action anchors above.	2 / 5
Completeness	It states both a 'what' ('Wix integration. Manage Stores.') and an explicit 'when' ('Use when the user wants to interact with Wix data'), but the 'what' is vague and the 'when' could be more specific, matching the 'has both what and when; when could be more explicit' anchor rather than the fully concrete score-5 anchor.	4 / 5
Trigger Term Quality	It includes relevant keywords ('Wix', 'Stores', 'interact with Wix data') but misses common variations and synonyms a user might say (eCommerce, products, orders, store catalog), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Wix is a specific named platform with a distinct trigger ('interact with Wix data'), giving a clear niche with only minor overlap risk against other eCommerce/store skills, so it sits at 'mostly distinct' rather than the fully distinct score-5 anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/wix/SKILL.md
Commit: f484c82

Reviewed: 3 days 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.