Skills wp-block-development

📦

wp-block-development

Name: wp-block-development
Author: Automattic

Content revision r2 Safe ⚙️ External commands📁 Filesystem access

Build and Maintain WordPress Blocks

WordPress block changes can break registration, saved content, or editor behavior. This skill guides implementation, migration, debugging, and verification for Gutenberg blocks.

Supports: Claude Codex Code(CC)

🥈 81 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "wp-block-development" from https://skillstore.io/skills/automattic-wp-block-development.md and its manifest at https://skillstore.io/api/skills/automattic-wp-block-development/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/automattic-wp-block-development.md Signed manifest GET /api/skills/automattic-wp-block-development/manifest Signed lockfile GET /api/skills/automattic-wp-block-development/lockfile

Test it

Using "wp-block-development". Review the testimonial block before adding a rating attribute.

Expected outcome:

The review identifies where attributes are stored, checks saved markup compatibility, and recommends a migration plus save-and-reload verification.

Using "wp-block-development". Plan a dynamic event listing block.

Expected outcome:

Use metadata-based PHP registration and server rendering.
Keep saved content minimal and apply standard wrapper attributes.
Verify editor previews, frontend output, assets, escaping, and tests.

Using "wp-block-development". Find why a block is missing from the inserter.

Expected outcome:

The diagnosis checks the block name, metadata validity, server registration, build output, and editor console before proposing focused changes.

Security Audit

Safe

v11 • 7/23/2026 Open versioned report

All 66 static findings are false positives caused by Markdown code formatting, ordinary WordPress terminology, or bounded read-only filesystem inspection. No command execution, credential access, prompt injection, network activity, file modification, or malicious intent was found.

Files scanned

601

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/automattic-wp-block-development/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/automattic-wp-block-development/security.svg)](https://skillstore.io/skills/automattic-wp-block-development?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/automattic-wp-block-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/automattic-wp-block-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/automattic-wp-block-development.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

Automattic. (2026). wp-block-development security audit report (audit version 11) [Author version unspecified]. Skillstore. https://skillstore.io/skills/automattic-wp-block-development/audits/11

BibTeX citation

@techreport{automattic-automattic-wp-block-development-2026,
  author = {Automattic},
  title = {wp-block-development security audit report (audit version 11)},
  institution = {Skillstore},
  year = {2026},
  number = {11},
  url = {https://skillstore.io/skills/automattic-wp-block-development/audits/11},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wp-block-development security audit report (audit version 11)"
version: "unspecified"
type: report
authors:
  - name: "Automattic"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/automattic-wp-block-development/audits/11"
identifiers:
  - type: other
    value: "skillstore:automattic-wp-block-development:audit:11"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Create a New Block

Scaffold a block, define metadata, choose a rendering model, and verify editor and frontend behavior.

Repair Invalid Content

Trace serialization mismatches, attribute problems, and missing deprecations that produce invalid block warnings.

Modernize Block Architecture

Move existing blocks toward apiVersion 3, metadata registration, modern scripts, and compatible migrations.

Try These Prompts

Inspect a Block

Inspect the block in [path]. Explain its metadata, registration, rendering model, attributes, and required verification steps.

Create a Block

Create a [static or dynamic] WordPress block named [namespace/name] in [path] for WordPress [version]. Include tests and verification.

Fix Invalid Content

Diagnose the invalid block warning in [path]. Compare current saved markup with prior behavior and propose a compatible migration.

Plan a Block Migration

Modernize blocks under [path] for WordPress [version]. Assess apiVersion, registration, rendering, assets, deprecations, translations, and automated test coverage.

Best Practices

Confirm the repository, block path, and supported WordPress versions before editing.
Keep block names and serialized markup stable, or add explicit deprecations and migrations.
Run repository build, lint, tests, insertion, save, reload, and frontend checks.