CtrlK
BlogDocsLog inGet started
Tessl Logo

block-creator

Create, edit, build, and review a custom WordPress Gutenberg block plugin inside a Studio-backed site.

60

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/codex/plugins/wordpress-studio/skills/block-creator/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is well-structured, concise, and has a clear workflow with error-recovery feedback, but it stops short of providing copy-paste templates for the actual block scaffold files, which is the main actionability gap. No bundle files exist to support progressive disclosure beyond the single file.

Suggestions

Add minimal copy-paste templates (or a referenced scaffold file) for block.json, src/index.js, src/edit.js, src/save.js, and src/render.php so the core artifact is executable, not just named.

Insert an explicit validation checkpoint after the build (e.g. 'Verify build/ contains index.js and the block registers in the editor') to move workflow clarity toward 5.

Move the per-file rules (view.js plain JS, editor/frontend matching, preferred controls) into a short referenced reference file to keep SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

The body is lean and directive (short bullets, concrete rules like 'no JSX / no React / no imports from @wordpress/*') and assumes Claude's competence; minor redundancy such as restating 'Use the selected Studio site as the root' keeps it just below the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Build commands ('pnpm exec wp-scripts build'), PHP guards ('if ( ! defined( "ABSPATH" ) ) { exit; }'), escaping functions, and component names are concrete, but the core scaffold files (block.json, edit.js, save.js, render.php, view.js) are only listed by name with rules rather than given as copy-paste templates, leaving key executable details missing per anchor 3.

3 / 5

Workflow Clarity

A clear numbered scaffold workflow (steps 1-6) is paired with an explicit error-recovery feedback loop ('read the full error output... fix only the relevant file... retry up to 3 times'), but validation is mostly implicit (build pass/fail) rather than an explicit checkpoint, matching anchor 4.

4 / 5

Progressive Disclosure

The skill is a single well-sectioned file with no nested or buried references and easy navigation; because it exceeds 50 lines the simple-skill 5-exception does not apply, so it sits at anchor 4 (good structure, minor organization gaps) rather than 5.

4 / 5

Total

15

/

20

Passed

Description

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

The description is specific and well-targeted to a distinct niche, but it omits an explicit 'Use when...' trigger clause, which the rubric caps at completeness 3. Adding a trigger phrase would lift the weakest dimension.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to create or modify a custom Gutenberg block inside a local Studio site.'

Sharpen the generic 'review' action into a concrete verb (e.g. 'validate the built block in the editor') to push specificity toward 5.

Include a common synonym such as 'custom block' alongside 'Gutenberg block' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('custom WordPress Gutenberg block plugin') and four concrete actions ('Create, edit, build, and review'), but 'review' is generic and 'create'/'build' overlap, leaving minor coverage gaps consistent with anchor 4 rather than the fully comprehensive anchor 5.

4 / 5

Completeness

The description gives a clear 'what' but contains no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 3; the 'when' lives only in the body, not the description field.

3 / 5

Trigger Term Quality

Natural user-facing terms 'WordPress', 'Gutenberg block', and 'block plugin' are present and would be said by users needing this skill; a few common synonyms (e.g. 'custom block', 'block plugin') are only weakly covered, stopping short of anchor 5's comprehensive synonym list.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined ('custom WordPress Gutenberg block plugin inside a Studio-backed site') with distinct triggers and minimal overlap with other skills, matching anchor 5.

5 / 5

Total

16

/

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.