CtrlK
BlogDocsLog inGet started
Tessl Logo

wix-design-system

Wix Design System component reference. Use when building UI with @wix/design-system, choosing components, checking props and examples, or writing tests with component testkits. Triggers on "what component", "how do I make", "WDS", "show me props", "testkit", "driver", or component names like Button, Card, Modal, Box, Text.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

The body is a well-structured, executable navigator: lean command-driven workflow with clear sequencing, a direct-access fallback, and one-level-deep references to a verified bundle. All dimensions score at the top anchor.

DimensionReasoningScore

Conciseness

The body is lean: terse command snippets and one-line descriptions of output with no padding or explanation of concepts Claude already knows, matching the "every token earns its place" anchor.

3 / 3

Actionability

Every step gives fully executable commands with concrete arguments (e.g. `node $WDS component Button`, `node $WDS example Button "Loading state"`), copy-paste ready and not pseudocode.

3 / 3

Workflow Clarity

A clear five-step lookup sequence with each step stating its command and expected output, plus an explicit fallback path; no destructive/batch operations so the missing-validation cap does not apply, and the batch form documents error handling.

3 / 3

Progressive Disclosure

SKILL.md is an overview that points to a real one-level-deep reference (references/file-structure.md) and bundles scripts/wds.cjs, both verified to exist, with the deep file-format detail kept out of the main body.

3 / 3

Total

12

/

12

Passed

Description

100%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, concise description that states concrete capabilities, explicit usage triggers, natural trigger phrases, and a clearly distinct niche around the Wix Design System. All four dimensions land at the top anchor.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ("choosing components, checking props and examples, or writing tests with component testkits") rather than vague language, matching the top anchor.

3 / 3

Completeness

It explicitly answers both what it does ("Wix Design System component reference") and when to use it ("Use when building UI with @wix/design-system...") with an explicit "Triggers on..." clause.

3 / 3

Trigger Term Quality

It provides broad coverage of natural phrases users would say ("what component", "how do I make", "WDS", "show me props", "testkit", "driver") plus component names like Button, Card, Modal, Box, Text.

3 / 3

Distinctiveness Conflict Risk

It names a specific niche (@wix/design-system) with distinctive triggers and component names, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

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.