DOWNLOADABLE CODEX SKILL · v1.0.0
Check Gutenberg and plugin block markup before a WordPress change ships.
By Abdessalam · Updated
THE WORKFLOW
Check Gutenberg and plugin block markup before a WordPress change ships. It keeps the work tied to evidence and the project’s actual constraints.
The user asks to diagnose invalid blocks, editor warnings, or fragile generated markup. Download the package, inspect its instructions, and adapt its review notes to the project.
EXAMPLE REQUEST
$aboutcodex-wp-block-compatibility Check this Gutenberg page after the plugin update and repair any invalid block markup without replacing the design.A scoped compatibility finding or fix with parser, editor, and front-end evidence.
Inspect the extracted package first. For a local project, place the skill folder here:
.agents/skills/aboutcodex-wp-block-compatibility/SKILL.mdOpen the project and inspect the Skills sidebar to locate the skill by name. Follow the skill controls available in your current desktop application.
Open the project in Codex CLI. Use /skills or $aboutcodex-wp-block-compatibility to select the skill explicitly.
Open the project in the Codex IDE extension. Use /skills or $aboutcodex-wp-block-compatibility to select the skill explicitly.
Verify discovery: locate the exact skill name before starting. If missing, check the folder, SKILL.md filename, and name/description frontmatter, then restart the client.
After selecting the skill, use this inspection request:
Read the aboutcodex-wp-block-compatibility skill. Explain its purpose, inputs, and boundaries. Do not edit files or run its workflow yet.Documentation-based guidance, checked September 10, 2026. Client discovery was not independently tested here. OpenAI’s skill documentation. Troubleshoot installation
aboutcodex-wp-block-compatibility/SKILL.md1 KBaboutcodex-wp-block-compatibility/references/NOTES.md444 Baboutcodex-wp-block-compatibility/LICENSE.txt1 KB---
name: "aboutcodex-wp-block-compatibility"
description: "Check Gutenberg and plugin block markup before a WordPress change ships. Use when the user asks to diagnose invalid blocks, editor warnings, or fragile generated markup."
---
# Check WordPress block compatibility
Check Gutenberg and plugin block markup before a WordPress change ships.
## Workflow
1. Inventory the affected core and plugin blocks from parsed content or editor output.
2. Compare saved markup, attributes, registered block support, and rendered HTML without normalizing content prematurely.
3. Locate whether the defect belongs to saved content, a render callback, theme CSS, or a missing plugin.
4. Apply the smallest authorized correction and preserve block ownership and editability.
5. Reparse the changed content and open representative editor and front-end views when access is available.
Read `references/NOTES.md` before finalizing the work. Follow project instructions and the user's authorized scope. Use available evidence, label assumptions, and never report a check as passing unless it actually ran.
## Deliverable
A scoped compatibility finding or fix with parser, editor, and front-end evidence. State material limitations and link to changed files or rendered evidence when available.
Cannot prove compatibility with unavailable premium plugins or browsers. Human review remains necessary for content changes.
Structure checked · 2026-09-10
Required frontmatter, folder layout, file inventory, validator run, and generated ZIP round-trip checked. Workflow behavior has not been independently evaluated.
Package checks confirm file structure. They do not establish that a skill works well on every task.
1.0.0 — Initial instruction-only release with supporting review notes.
Progress stays in this browser. No account needed.
Added interface-specific guidance and a read-only inspection request. The downloadable package is unchanged.
What to do: No re-download needed for this documentation update. Inspect the current version and compare your local changes before replacing a skill.
This log starts with the first recorded review; it is not a reconstruction of earlier revisions.
THE ABOUTCODEX BRIEFING
One workflow to try, one change explained, and one resource to keep. Planned weekly.
Read the sample issue ↗Confirm your email to join. Unsubscribe anytime through a delivered newsletter. Privacy policy.