CtrlK
BlogDocsLog inGet started
Tessl Logo

block-creator

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

63

Quality

73%

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

81%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 content is a well-structured, terse, and highly actionable workflow for building Gutenberg blocks, with explicit sequencing, checkpoints, and an error-recovery loop. The only notable gaps are minor redundancy and the lack of file templates or reference files for the scaffolded files.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven, assuming Claude's competence (e.g., "no JSX, no React, use DOM APIs directly") with no padded concept explanations. Minor redundancy keeps it at anchor 4 rather than 5: the `function_exists` guard is stated twice (PHP bootstrap and PHP standards) and the site-as-root instruction is repeated.

4 / 5

Actionability

Concrete guidance dominates: exact plugin directory layout, an explicit 11-file scaffold list, executable commands ("pnpm install", "pnpm exec wp-scripts build"), a PHP guard snippet, and named WP components (`InspectorControls`, `RichText`, etc.). It stops short of anchor 5 because the scaffold files are listed without any example contents or templates for them.

4 / 5

Workflow Clarity

The workflow is explicitly sequenced (verify Studio readiness → resolve site → understand request → static/dynamic decision → identifiers → scaffold) with `record_workflow_event` start/complete checkpoints, post-build activation and test-page insertion steps, and a dedicated error-recovery loop (read full error → fix only the relevant file → rebuild → retry up to 3 times). This matches the anchor requiring clear sequencing with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

As a single-file skill with no bundle files, the body is well-sectioned with clear headers and mostly appropriate placement. It fits anchor 4 rather than 5 because at ~190 lines the per-file guidance (e.g., block.json, package.json, PHP bootstrap details) could reasonably be split into one-level-deep references, and the under-50-line simple-skill exception does not apply.

4 / 5

Total

17

/

20

Passed

Description

66%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 reasonably distinct, naming a clear domain and four concrete actions. Its main weakness is the absence of any "Use when..." trigger clause, which leaves the 'when should Claude use it' question only weakly implied and caps completeness.

Suggestions

Add an explicit "Use when..." clause, e.g., "Use when the user wants to create, modify, or build a custom Gutenberg block in a local WordPress Studio site."

Include a few natural trigger variations users would actually say, such as "custom block", "block plugin", or "block editor", to strengthen trigger-term coverage.

Mention a related lifecycle action (e.g., scaffolding or activating the block plugin) to round out coverage toward anchor 5 on specificity.

DimensionReasoningScore

Specificity

The description lists four concrete actions ("Create, edit, build, and review") on a specific artifact ("custom WordPress Gutenberg block plugin"), matching the several-specific-actions anchor. It falls short of anchor 5 because coverage has minor gaps (e.g., scaffolding, activation, debugging are not mentioned).

4 / 5

Completeness

The 'what' is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by "inside a Studio-backed site". Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural keywords like "WordPress", "Gutenberg block", "plugin", and "Studio-backed site" give good keyword coverage. A few natural variations users might say ("custom block", "block plugin", "editor block") are missing, so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche (custom Gutenberg block plugin inside a Studio-backed site) is mostly distinct with clear triggers, carrying only minor overlap risk with generic WordPress or plugin-development skills. This fits anchor 4; it is not anchor 5 because the boundary against general WordPress plugin work is not sharply drawn.

4 / 5

Total

15

/

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.

Validation — 16 / 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.