CtrlK
BlogDocsLog inGet started
Tessl Logo

wpds

Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, well-organized instruction skill that avoids over-explanation and gives clear scope boundaries, but its actionability is limited by the absence of concrete MCP query examples and its validation step is conditional rather than a hard checkpoint.

Suggestions

Add a minimal executable example showing a WPDS MCP resource call (e.g. how to fetch and read 'wpds://components/:name') so Claude has copy-paste-ready guidance.

Tighten the Validation step into an explicit validate -> fix -> re-run loop instead of the conditional 'use them ... when possible'.

Include one short worked example (a token or component lookup to a concrete UI decision) to bridge the gap between rules and execution.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, stating rules and boundaries without explaining what a design system or component is; every section earns its place and there is no padded concept explanation.

5 / 5

Actionability

Guidance is concrete in places (named MCP resource URIs like 'wpds://components/:name' and 'wpds://design-tokens'), but there is no executable code snippet or worked example showing how to query the MCP, so it stays at 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The flow is clear (read docs via MCP first, focus on UI, validate with local lint scripts, then recap), and the validation step ('use lint scripts to validate') acts as a checkpoint, but it is only weakly specified as conditional ('when possible') rather than an explicit validate-fix-retry loop.

4 / 5

Progressive Disclosure

This is a short single-purpose skill (under 50 lines, no bundle files) with well-organized sections (Prerequisites, When to use, Rules, Output), so under the simple-skill exception it qualifies for the top score without external file references.

5 / 5

Total

17

/

20

Passed

Description

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

A concise, well-structured description that clearly states both capability and trigger conditions using third-person voice. It is specific and distinctive, with only minor room to add more trigger synonyms.

DimensionReasoningScore

Specificity

The description names the domain ('building UIs leveraging the WordPress Design System') and lists several concrete targets ('components, tokens, patterns'), giving good action specificity, but 'building UIs leveraging' is slightly generic so it sits just below the comprehensive-coverage anchor.

4 / 5

Completeness

It explicitly answers 'what' ('building UIs leveraging the WordPress Design System and its components, tokens, patterns') and 'when' ('Use when building UIs leveraging...') with a concrete 'Use when' trigger clause, matching the top anchor.

5 / 5

Trigger Term Quality

It surfaces natural terms users would say ('WordPress Design System', 'WPDS', 'components', 'tokens', 'patterns') plus the WP acronym, but lacks common variations like specific package names or file extensions that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

The WordPress Design System niche is clearly scoped with distinct triggers ('WordPress Design System', 'WPDS', 'tokens', 'patterns') and minimal overlap risk with unrelated skills.

5 / 5

Total

18

/

20

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
WordPress/agent-skills
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.