wordpress-creator

Route WordPress build and audit requests to the right implementation path for a Studio-backed site. Use when the user wants WordPress work and it is not yet clear whether the task should be handled as site creation, theme work, a custom block, a plugin, or an audit.

Quality

85%

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

Quality

Content

86%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-structured router skill that adds only what Claude would not already know and organizes routing decisions clearly. It would benefit only marginally from a brief edge-case or ambiguity-resolution example.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: assumes Claude knows what blocks, plugins, and themes are and provides only routing rules and guardrails, with every line earning its place.	5 / 5
Actionability	Gives concrete, executable routing criteria ('Use site-creator when...') and a tie-break rule ('choose the smallest abstraction'), but as an instruction-only router it lacks code/commands, leaving minor guidance gaps for edge cases.	4 / 5
Workflow Clarity	Clear decision sequence via branch rules plus an explicit tie-break rule and guardrails; no validation checkpoints, but none are needed for a non-destructive routing decision, so it stays just below 5.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external bundle references; content is well-organized into Ownership, Routing rules, and Guardrails sections, satisfying the simple-skill exception for a 5.	5 / 5
	Total	18 / 20 Passed

Description

83%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 well-crafted router description that clearly states its purpose and gives an explicit, scenario-rich 'Use when' clause. It enumerates the routing targets concretely and is unlikely to trigger for unrelated skills.

Dimension	Reasoning	Score
Specificity	Names the WordPress domain and enumerates five concrete routing paths (site creation, theme work, custom block, plugin, audit), with the action being routing rather than a broad set of distinct operations — a few natural-action variations are absent, keeping it just below 5.	4 / 5
Completeness	Explicitly answers both what ('Route WordPress build and audit requests to the right implementation path') and when ('Use when the user wants WordPress work and it is not yet clear whether...') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('WordPress build', 'audit', 'site creation', 'theme work', 'custom block', 'plugin') with good synonym coverage, though a few common phrasings users might say are not exhaustively listed.	4 / 5
Distinctiveness Conflict Risk	Clear niche as a router across five named sibling skills with an explicit 'not yet clear which path' disambiguator, though it inherently overlaps with the specialist skills it routes to.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Automattic/build-with-wordpress
Path: skills/wordpress-creator/SKILL.md
Commit: b4fc8b7

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