Name: wp-block-development
Rating: 74.4 (1 reviews)
Author: WordPress

wp-block-development

Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.

Quality

92%

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

92%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, concise procedural skill with explicit verification checkpoints, an error-recovery section, and clean one-level-deep references that all resolve to real files. The main gap is that inline executable code is sparse, with most detail deferred to reference files.

Suggestions

Inline one short copy-paste example for the most common task (e.g., a minimal block.json or a register_block_type_from_metadata snippet) so the skill is executable without opening a reference.

Add an explicit 'if X fails, do Y' tie between the Verification checklist and the Failure-modes section so the feedback loop is a single connected path rather than two separate sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: short numbered steps, bullets, and named APIs with no padding about what WordPress or blocks are; the only explanatory block (apiVersion 3 / iframe editor) conveys non-obvious version-specific facts rather than generic concepts, fitting the lean-and-efficient anchor.	5 / 5
Actionability	It gives concrete commands (node scripts/list_blocks.mjs, @wordpress/create-block) and specific APIs (useBlockProps(), get_block_wrapper_attributes(), useInnerBlocksProps()), but most sections defer full code to references/*.md rather than providing copy-paste snippets inline, fitting the mostly-executable-with-minor-gaps anchor at 4 rather than the copy-paste-ready anchor at 5.	4 / 5
Workflow Clarity	A clearly numbered 0–10 procedure with an explicit Inputs section, a dedicated Verification section of concrete checkpoints, and a Failure-modes/debugging feedback loop, matching the anchor requiring explicit validation steps and error-recovery feedback loops.	5 / 5
Progressive Disclosure	The body is a well-organized overview with one-level-deep 'Read: references/X.md' signals; all ten referenced files exist in ./references and the list_blocks.mjs script exists, so navigation is clean with no nested references, matching the clear-overview anchor.	5 / 5
	Total	19 / 20 Passed

Description

92%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, highly specific description that explicitly pairs a natural trigger clause with a comprehensive concrete capability list and a well-scoped niche. The only slight weakness is that trigger coverage leans on API jargon over lay synonyms.

Suggestions

Add one or two plain-language trigger synonyms (e.g., 'Gutenberg editor', 'block plugin') so non-API-fluent users land on this skill.

Consider a file/extension cue (e.g., 'block.json files') alongside the API names to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete technical actions/sub-areas (block.json metadata, register_block_type(_from_metadata), attributes/serialization, dynamic rendering via render.php/render_callback, deprecations/migrations, viewScript vs viewScriptModule, build/test workflows), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	It explicitly answers both 'when' ('Use when developing WordPress (Gutenberg) blocks:') and 'what' (a concrete colon-delimited list of capabilities), matching the anchor that requires explicit concrete trigger phrases for both.	5 / 5
Trigger Term Quality	'Use when developing WordPress (Gutenberg) blocks' is a natural user phrase and Gutenberg is a good synonym, but the bulk of the description is API-level jargon (register_block_type, viewScriptModule) with a few natural user-voice synonyms/file extensions missing, fitting the good-but-not-comprehensive anchor at 4.	4 / 5
Distinctiveness Conflict Risk	The description targets a clear niche (WordPress Gutenberg blocks with specific APIs) with distinct triggers and minimal overlap risk with other skills, matching the clear-niche anchor.	5 / 5
	Total	19 / 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
referenced_paths_exist	Referenced path issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: WordPress/agent-skills
Path: skills/wp-block-development/SKILL.md
Commit: d87ee69

Reviewed: about 13 hours 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.