CtrlK
BlogDocsLog inGet started
Tessl Logo

block-creator

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

58

Quality

66%

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/claude-code/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 skill body is well-structured, concise, and has a clear workflow with error-recovery feedback loops. Its main weakness is actionability: it lists the files to create and rules for them but omits copy-paste-ready templates for the core block files.

Suggestions

Add minimal copy-paste templates for block.json, src/index.js, src/edit.js, and src/save.js so the core files are executable rather than only described.

Add an explicit verification step after build (e.g. confirm the block appears and renders in the editor/frontend) to strengthen workflow validation.

Consider moving detailed per-file guidance into a references file and keeping SKILL.md as an overview, which would improve progressive disclosure for a >50-line skill.

DimensionReasoningScore

Conciseness

The body is lean with bullet lists and minimal padding, avoiding explanations of concepts Claude already knows; a few generic lines (e.g. "Keep the implementation consistent with standard Gutenberg block conventions") could be trimmed, placing it just below the top anchor.

4 / 5

Actionability

Concrete commands (pn install, wp-scripts build), directory layout, a PHP guard snippet, and named components are present, but no full file templates for block.json/index.js/edit.js/save.js are provided, leaving key executable details missing.

3 / 5

Workflow Clarity

A clear six-step workflow is sequenced with checkpoints (build success, activation, record_workflow_event stages) and an error-recovery feedback loop (read error, fix, rebuild, retry up to 3 times), with only minor validation gaps.

4 / 5

Progressive Disclosure

The content is well-organized into clearly headed sections with no buried or nested references; at over 50 lines with no external bundle files it stays just below the top anchor, but structure and placement are good.

4 / 5

Total

15

/

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 concise, specific, and occupies a clear niche, but it lacks an explicit 'Use when…' trigger clause, which caps its completeness. Adding a natural-language trigger condition would raise both completeness and trigger quality.

Suggestions

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

Add common synonyms such as "custom block" or "block plugin" to broaden natural trigger coverage.

Clarify what "review" entails (e.g. "review block output in the editor and frontend") to strengthen specificity.

DimensionReasoningScore

Specificity

The description lists four concrete actions ("Create, edit, build, and review") on a clearly named domain (custom WordPress Gutenberg block plugin), matching the anchor that lists several specific actions with minor coverage gaps.

4 / 5

Completeness

The "what" is clearly stated, but there is no explicit "Use when…" trigger clause, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say are present ("WordPress", "Gutenberg block", "block plugin", "Studio-backed site"), giving good keyword coverage, though some common synonyms (e.g. "custom block") are not exhaustively covered.

4 / 5

Distinctiveness Conflict Risk

The niche is specific (custom Gutenberg block plugin inside a Studio-backed site) with minimal overlap risk, but the absence of an explicit trigger phrase keeps it just below the top anchor.

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.

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.