wpds

WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.

Quality

46%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

40%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 well-organized but is a catalogue advertisement rather than a working skill: it defers everything substantive to an external repository and provides no executable guidance for the stated purpose. Sections and pointer signaling are clean, but actionability and workflow are stubs.

Suggestions

Provide the actual design-token, typography, and component-pattern guidance (or bundle it in references/) instead of a pointer to the upstream GitHub repo, so the skill is usable without external fetching.

Replace 'install the upstream bundle into your active agent's skills directory' with a concrete, executable install command.

Trim duplication: the 'What it does' and 'Source' sections restate the frontmatter description and upstream/category fields verbatim.

Dimension	Reasoning	Score
Conciseness	The body is lean and doesn't explain concepts Claude already knows, but 'What it does' repeats the frontmatter description verbatim, the 'Source' section re-states upstream/category already in frontmatter, and the blockquote adds nothing — 'mostly efficient but could be tightened'.	3 / 5
Actionability	Despite a purpose of applying WordPress design tokens, the body contains no guidance toward that task; the only executable command is 'open https://github.com/WordPress/skills' and 'install the upstream bundle into your active agent's skills directory' is a high-level hint with no concrete install step — 'minimal concrete guidance; missing the specific steps to execute'.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream README → install bundle → invoke by name or triggers) but the central install step is undefined and the sequence never reaches the skill's actual task, matching 'rough sequence present but many gaps; steps poorly defined'.	2 / 5
Progressive Disclosure	Sections are clear and well-labeled and the single external reference (the GitHub repo) is explicitly signaled one level deep, with no bundled files misplaced. Not 5 because all substantive content is deferred to an unbundled external repo rather than packaged reference files, taking the disclosure path entirely outside the skill.	4 / 5
	Total	11 / 20 Passed

Description

53%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 clearly states what the skill does with a well-defined WordPress-theming niche, but it has no 'when to use' guidance and misses natural trigger phrasings users would say. It reads as a domain statement rather than a complete discoverable description.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when styling or building WordPress themes, or when the user mentions WordPress design, WP tokens, or matching WordPress's official look and feel.'

Enumerate the concrete operations (e.g. converting design tokens to CSS custom properties, applying typography scales, restyling components) instead of a single 'apply' verb over a list of artifacts.

Include natural synonyms and variations users would actually say (WP, WordPress theme, brand colors) rather than relying on the jargon-leaning triggers field.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and artifacts ('Apply WordPress's official design tokens, typography, and component patterns to themes and sites') but boils down to a single apply-verb over a list of objects, with no specific operations enumerated — matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than 'lists several specific actions'.	3 / 5
Completeness	The 'what' is clear (apply WordPress design tokens, typography, and component patterns) but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Relevant keywords are present (WordPress, design tokens, typography, component patterns, themes, sites) but common natural variations users would actually say (WP, WordPress theme, brand colors, file types) are missing. The separate frontmatter triggers field ('wpds', 'wp tokens') leans jargon and is not part of the description.	3 / 5
Distinctiveness Conflict Risk	'WordPress's official design tokens ... to themes and sites' carves a clear niche that is unlikely to trigger for unrelated skills, with only minor overlap risk against closely related brand/design-system skills.	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: nexu-io/open-design
Path: skills/wpds/SKILL.md
Commit: 1b47e60

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.