Wp Block Development

What it does

This workflow follows a block from repository discovery through metadata, registration, attributes, editor behavior and server rendering. It gives particular attention to serialization changes and deprecations, which matter because old posts can become invalid even when a newly inserted block appears to work correctly.

Best for

WordPress developers creating blocks or changing existing blocks already used in published content.

Tradeoffs and requirements

The supported core version determines which metadata and script-module features are available. Build success alone does not establish backward compatibility, and replacing saved markup without an appropriate migration can affect existing posts.

Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/WordPress/agent-skills/tree/eff3785fc28c4380d172094518c66a6a997c95d4/skills/wp-block-development --skill wp-block-development

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

No configured text patterns matched. Unmatched or concealed behavior can still exist.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

Offline package integrity

A temporary folder-copy check, not an agent installation or runtime safety verdict.

12 files copied and checksummed from this exact source snapshot. No package code or installation scripts were executed.

Inventory SHA-256: 08b3a0b4ca9351ea7ed4e49581a3749618aa9e7da0d767af7d001092d1891a45

Isolated helper checks

Selected helper behavior only. Full agent compatibility and runtime safety remain unverified.

4 synthetic scenarios passed for skills/wp-block-development/scripts/list_blocks.mjs, checked 2026-10-29. The container had no network, production data or credentials, and only read-only fixture and helper mounts.

Script SHA-256: 01bd752371dd13d3e8c0b1f7a240eed382c0177594449c102e8853a288023951

AI Craft Pad Skill Score

75/100 · Metadata coverage 80% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

0/100

0

Repository Health

85/100

85

Compatibility Evidence

80/100

80

Popularity

61/100

61

Originality

80/100

80

Static Safety

60/100

60

Supporting-file static inspection

Bounded source inspection, not a runtime security audit. This inspection does not execute code.

1 text files inspected at this exact repository snapshot. 10 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.

Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.

Suggested workflow

Locate existing block definitions, identify static versus dynamic rendering and inspect the current build tooling. Make a focused metadata or implementation change, preserving established attributes and adding a deprecation path when stored content needs to evolve.

How to judge the result

Open both new and previously saved examples in the editor, save and reload them, and inspect frontend output. Check dynamic rendering, nested blocks and missing attributes where relevant. Record the tested core versions and any deliberately unsupported legacy content.