Wp Block Development
WordPress block editor review for Codex. Use when reviewing block.json, editor components, save and render patterns, attributes, InnerBlocks, deprecations, build setup, or the Interactivity API in Gutenberg blocks.
Install
$ agentstack add skill-jorgerosal-wordpress-skills-wp-block-development ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jorgerosal-wordpress-skills-wp-block-development) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Codex WordPress Block Development Review
Purpose
Use this skill when Codex should review WordPress block code across both PHP and JavaScript or JSX, with special attention to block.json, editor behavior, rendering, and block lifecycle correctness.
Focus Areas
block.jsonschema and registration fieldseditandsaveimplementation quality- Render callbacks and render files
- Attribute schemas, deprecations, and validation issues
InnerBlocks,useBlockProps, and editor component patterns- Interactivity API and source/build workflow concerns
Workflow
- Identify whether the code is a single block, block library, theme block, or mixed plugin.
- Validate
block.jsonand registration flow first. - Review
edit,save, and dynamic rendering behavior. - Check for block-specific risks such as nondeterministic save output, deprecated patterns, and broken
InnerBlockshandling. - Pull only the needed shared reference docs before finalizing findings.
Reference Files
Load only the references you need from:
../../claude-skills/wp-block-development/references/block-json-guide.md../../claude-skills/wp-block-development/references/editor-patterns.md../../claude-skills/wp-block-development/references/dynamic-blocks-guide.md../../claude-skills/wp-block-development/references/interactivity-api-guide.md
Output
- Include both PHP and JS or JSX file references where relevant
- Group findings by severity
- Explain block-editor impact, frontend impact, or validation impact
- Suggest fixes that align with current Gutenberg patterns
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jorgerosal
- Source: jorgerosal/wordpress-skills
- License: MIT
- Homepage: https://jorgerosal.github.io/wordpress-skills/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.