CtrlK
BlogDocsLog inGet started
Tessl Logo

wp-patterns

Generate technically correct, design-distinctive WordPress block patterns. Use when creating block patterns, starter page patterns, template patterns, template part patterns, or improving pattern design quality. Covers pattern registration (PHP headers, auto/manual), block markup syntax, theme.json design tokens, categories, template types, accessibility, and i18n/escaping.

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear, validated workflow and well-structured progressive disclosure into real reference files. Its main weakness is verbosity — several sections overlap and could be consolidated to respect the token budget.

Suggestions

Consolidate overlapping guidance: the 'High-impact visual patterns' and 'Pattern-specific decisions' sub-sections restate ideas from the five design decisions and could be merged or trimmed.

Move the design-decision tables (tone/composition/typography/color) into a reference file, keeping only a compact pointer plus the must-make-five-decisions rule in the main body.

Trim the Failure modes list to the highest-signal items and link the rest from anti-patterns.md to reduce inline length.

DimensionReasoningScore

Conciseness

The body is accurate and largely earns its place, but at ~290 lines with multiple overlapping sections (design decisions, high-impact visual patterns, pattern-specific decisions, plus full checklists and failure modes) it is verbose and could be tightened without losing clarity.

2 / 3

Actionability

Provides concrete, executable guidance: a PHP file-header block, nesting-tree example, specific preset slugs, triage/detect script commands, and an `npx @wp-playground/cli` verification command — copy-paste ready.

3 / 3

Workflow Clarity

A clearly sequenced procedure (triage → design → plan → write → quality check → technical validation → verification) with explicit validation checklists, block-recovery error feedback, and a dedicated failure-modes/debugging section.

3 / 3

Progressive Disclosure

Well-signaled, one-level-deep references to real files (pattern-registration.md, block-markup-reference.md, anti-patterns.md, design-with-tokens.md, pattern-categories-and-types.md), with the overview keeping detailed syntax and PHP rules in those bundles.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concise, concrete, and fully answers what the skill does and when to use it, with natural trigger terms and a distinct niche. It is a strong, low-conflict description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and sub-capabilities: 'Generate technically correct, design-distinctive WordPress block patterns' plus 'Covers pattern registration (PHP headers, auto/manual), block markup syntax, theme.json design tokens, categories, template types, accessibility, and i18n/escaping.'

3 / 3

Completeness

Explicitly answers both what (generate patterns; covers registration, markup, tokens, categories, types, a11y, i18n/escaping) and when ('Use when creating block patterns, starter page patterns...').

3 / 3

Trigger Term Quality

Includes natural terms users would say — 'block patterns, starter page patterns, template patterns, template part patterns, or improving pattern design quality' — covering the common phrasings a user would reach for.

3 / 3

Distinctiveness Conflict Risk

A clear, narrow niche (WordPress block patterns) with distinct triggers, unlikely to fire for adjacent skills; cross-routing to wp-block-development and wp-interactivity-api is handled in the body.

3 / 3

Total

12

/

12

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.