wpds

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

Quality

49%

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

36%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 content functions as a catalogue advertisement pointing to an upstream repo rather than an actionable skill body, so it offers little executable guidance or workflow for applying WordPress design tokens. Its saving grace is brevity, though it is padded with restated frontmatter information.

Suggestions

Replace the off-repo GitHub pointer with concrete, executable instructions (e.g., sample token application commands or code snippets) so Claude can act without fetching the upstream repo.

Remove the redundant 'What it does' and 'Source' sections that merely restate the frontmatter description and upstream URL.

Add a clear sequenced workflow with validation checkpoints for applying tokens/patterns, or include local reference files (references/, scripts/) the body can point to for progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is short but padded with redundancy: the 'What it does' section restates the frontmatter description verbatim and 'Source' repeats the upstream URL already in frontmatter, so it is mostly efficient with unnecessary repetition.	3 / 5
Actionability	The 'How to use' section provides no executable guidance for the skill's stated purpose; its only command is `open https://github.com/...` to inspect a README and it delegates to 'ask the agent', leaving the specific steps missing.	2 / 5
Workflow Clarity	Only a rough install/discovery sequence is present (inspect README, install upstream bundle, invoke by name) with many gaps and no validation checkpoints for the skill's actual operation.	2 / 5
Progressive Disclosure	The body is sectioned but there are no bundle files and the only reference is an external GitHub URL rather than local, clearly-signaled reference files, so navigation to the actual content is indirect.	3 / 5
	Total	10 / 20 Passed

Description

62%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 is specific and well-differentiated, clearly conveying what the skill does and scoping it to WordPress. Its main weakness is the absence of an explicit 'Use when...' trigger clause and somewhat thin natural-keyword coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building or restyling WordPress themes and sites, or when the user mentions WordPress design tokens, typography, or component patterns.'

Expand the trigger terms with natural variations users actually say, such as 'design tokens', 'wp design', and 'WordPress theme styling'.

Make the capability actions more concrete by naming specific token types or component categories rather than the generic 'component patterns'.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions ('design tokens, typography, and component patterns'), but these are category-level rather than fully granular, leaving minor gaps in coverage.	4 / 5
Completeness	It has a clear 'what' (apply tokens/typography/components to themes and sites) but no explicit 'Use when...' clause, so per the judging guidelines completeness is capped at 3 with only weakly implied 'when'.	3 / 5
Trigger Term Quality	The frontmatter triggers ('wordpress design', 'wp tokens', 'wp design system', 'wpds') include some relevant natural keywords but miss common variations and synonyms like 'design tokens' or 'wp design'.	3 / 5
Distinctiveness Conflict Risk	'WordPress Design System' with WordPress-specific triggers carves a clear niche with minimal overlap risk against non-WordPress design skills.	5 / 5
	Total	15 / 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: d4138ea

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.