CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

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

The canonical home for this skill is wordpress-creator in Automattic/build-with-wordpress

SKILL.md
Quality
Evals
Security

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 gives concrete routing criteria and guardrails without over-explaining. Its main gap is the absence of worked examples showing ambiguous requests being resolved, which would lift actionability from good to excellent.

Suggestions

Add 1-2 worked examples of an ambiguous user request (e.g. 'make a rotating testimonial section') walked through the routing rules to a single chosen path, to lift actionability.

Include an explicit confirmation/checkpoint step before handing off (e.g. 'State the chosen path and why before invoking the specialist skill') to strengthen workflow clarity.

Clarify the 'aleady installed' typo in the block-creator rule and the duplicate 'Do not reach for a plugin' guardrail phrasing to tighten the guidance.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or over-explanation of concepts Claude already knows; every line (Ownership, Routing rules, Guardrails) earns its place.

5 / 5

Actionability

Routing rules give concrete, executable decision criteria ("Use site-creator when the user wants a new site...") and the guardrails are specific, but there are no worked examples of an ambiguous request being resolved to a single path.

4 / 5

Workflow Clarity

The decision workflow is clearly sequenced (evaluate request against rules, pick the smallest fitting abstraction, hand off to the specialist) with an explicit tie-breaker rule; it is not a destructive/batch operation so the validation cap does not apply, but no explicit confirmation checkpoint before handoff.

4 / 5

Progressive Disclosure

At under 50 lines with no need for external references, the content is split into clearly labeled sections (Ownership, Routing rules, Guardrails) with no nested references, satisfying the simple-skill exception for a top score.

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 strong, third-person description that clearly answers both what and when with concrete trigger phrases and a well-defined routing niche. It could be marginally improved by adding a few more natural synonyms, but it is already highly actionable and distinct.

DimensionReasoningScore

Specificity

The description names the concrete action ("Route WordPress build and audit requests to the right implementation path") and enumerates five specific routing targets (site creation, theme work, block, plugin, audit), giving several specific actions with only minor coverage gaps.

4 / 5

Completeness

It explicitly states both what the skill does ("Route WordPress build and audit requests to the right implementation path") and when to use it ("Use when the user wants WordPress work and it is not yet clear whether..."), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ("Use when the user wants WordPress work", "site creation", "theme work", "a custom block", "a plugin, or an audit") with good keyword coverage, though a few common synonyms/variations are missing.

4 / 5

Distinctiveness Conflict Risk

The "not yet clear whether the task should be handled as..." qualifier carves a distinct decision-maker niche with minimal conflict risk, though there is inherent minor overlap with the specialist skills it routes to.

4 / 5

Total

17

/

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
Automattic/build-with-wordpress
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.