block-creator
Create, edit, build, and review a custom WordPress Gutenberg block plugin inside a Studio-backed site.
53
58%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/claude-code/skills/block-creator/SKILL.mdQuality
Discovery
67%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 strong in specificity and distinctiveness, clearly identifying a narrow domain (WordPress Gutenberg block plugins in Studio-backed sites) with multiple concrete actions. However, it lacks an explicit 'Use when...' clause which caps completeness, and could benefit from additional natural trigger terms that users might employ when requesting this type of work.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks to create or modify a WordPress Gutenberg block, develop a custom block plugin, or work with the block editor in a Studio-backed site.'
Include additional natural trigger terms like 'custom block', 'block editor', 'wp plugin', 'WordPress plugin development', or 'register block type' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, edit, build, and review a custom WordPress Gutenberg block plugin inside a Studio-backed site.' This names four distinct actions and specifies the exact domain (WordPress Gutenberg block plugin in a Studio-backed site). | 3 / 3 |
Completeness | Clearly answers 'what does this do' (create, edit, build, review a Gutenberg block plugin), but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. The 'when' is only implied. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'WordPress', 'Gutenberg', 'block plugin', and 'Studio-backed site', but misses common user variations such as 'wp', 'block editor', 'custom block', 'gutenberg block', '.php', or mentioning specific block types. Users might not always say 'Studio-backed site'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: WordPress Gutenberg block plugins specifically within a Studio-backed site. This is unlikely to conflict with general WordPress skills, generic coding skills, or other plugin development skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive workflow for creating WordPress Gutenberg blocks within Studio sites, with good structural organization and reasonable error recovery guidance. Its main weaknesses are the lack of concrete, executable code examples for the scaffolded files (the skill tells Claude what files to create but not what to put in them) and some unnecessary explanation of concepts Claude already knows. The workflow would benefit from explicit validation checkpoints and example file contents.
Suggestions
Add concrete, executable code examples for at least the key scaffolded files (block.json, the PHP bootstrap, edit.js, save.js) so Claude has copy-paste-ready templates rather than vague guidance like 'Keep metadata valid and minimal'.
Add an explicit validation checkpoint after the build step—e.g., verify that the build/ directory contains the expected files (index.js, style-index.css, etc.) before proceeding to activation.
Remove or condense sections that explain things Claude already knows, such as PHP standards (no closing ?>, use esc_html) and the explanation of what view.js is—instead just state the constraint directly.
Consider splitting the detailed file guidance and core rules into a separate reference file to improve progressive disclosure and keep the main SKILL.md focused on the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary explanation (e.g., explaining when to use static vs dynamic blocks, what view.js is). Some sections like 'Defaults' and 'HTML rule' are terse and efficient, but the overall document could be tightened—Claude already knows WordPress/Gutenberg conventions and PHP standards like no closing tags. | 2 / 3 |
Actionability | The skill provides a clear file scaffold list and specific commands (pnpm install, wp-scripts build), but lacks executable code examples for the actual file contents (e.g., what goes in block.json, edit.js, the PHP bootstrap). The guidance is directional rather than copy-paste ready—phrases like 'Keep metadata valid and minimal' and 'Include build scripts that support the current task' are vague. | 2 / 3 |
Workflow Clarity | The workflow has clear numbered steps and covers the full lifecycle including error recovery with retry limits. However, validation checkpoints are weak—there's no explicit step to verify the build output before activation, no validation of block.json schema, and the error recovery section lacks specificity about common failure modes. The 'rebuild without reinstalling packages' is a good detail but the overall feedback loop could be more explicit. | 2 / 3 |
Progressive Disclosure | The skill references the 'studio' skill for review/iteration workflows, which is good delegation. However, with no bundle files provided, all content is inline in a single document that's fairly long. The file guidance sections (package.json, block.json, PHP bootstrap) could be split into reference files. The document structure uses headers well but could benefit from clearer navigation to separate quick-reference from detailed guidance. | 2 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Automattic/build-with-wordpress
- Commit
1c076c2
- 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.