CtrlK
BlogDocsLog inGet started
Tessl Logo

wp-block-themes

Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).

69

Quality

84%

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%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 well-structured skill body: concise, command-driven, with a clear triage-to-verification workflow and one-level-deep reference files that are all present. Actionability and workflow clarity are slightly held back by deferred detail and implicit rather than explicit validate-retry loops.

DimensionReasoningScore

Conciseness

Lean and efficient: it avoids explaining what block themes or theme.json are, lists concrete actions as bullets, and pushes detail to reference files; nearly every token earns its place.

5 / 5

Actionability

Provides concrete executable commands (the two `node .../scripts/*.mjs` invocations) and specific file paths to edit, but most steps defer to reference files rather than giving copy-paste-ready commands for theme.json/templates.

4 / 5

Workflow Clarity

Clear numbered procedure with a Verification section and Failure modes list; explicit checkpoints exist (re-run detect_block_themes after creating a theme) but validation feedback loops are implicit rather than fully spelled out.

4 / 5

Progressive Disclosure

Clean overview body with well-signaled, one-level-deep `references/*.md` pointers (all confirmed real files) and a single script; each section names the reference to read next, making navigation easy.

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 description: it names the domain, enumerates concrete capabilities, and opens with an explicit 'Use when' trigger clause covering the main scenarios. Slightly below perfect on specificity and trigger terms due to minor gaps in synonyms and breadth of troubleshooting detail.

DimensionReasoningScore

Specificity

Lists several concrete capability areas (theme.json global settings/styles, templates and template parts, patterns, style variations, Site Editor troubleshooting with style hierarchy, overrides, caching) rather than vague language.

4 / 5

Completeness

Explicitly states both what the skill does (the enumerated capability areas) and when to use it via the 'Use when developing WordPress block themes...' trigger clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('block themes', 'theme.json', 'templates', 'patterns', 'style variations', 'Site Editor', 'styles not applying'), though it omits common synonyms/file extensions like .json variants.

4 / 5

Distinctiveness Conflict Risk

Clear niche (WordPress block themes) with distinct triggers and minimal conflict risk; minor possible overlap with a generic WordPress or theme-development skill.

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