Agent skill

Wp Block Development

A skill your agent uses when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering…

GPL-3.0Auto-check passed

Install Wp Block Development

skills CLI

$ npx skills add gambitph/Stackable --skill wp-block-development -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install gambitph/Stackable wp-block-development --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/wp-block-development .claude/skills/wp-block-development && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "wp-block-development" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-block-development into .claude/skills/wp-block-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-block-development", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-block-development

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add gambitph/Stackable --skill wp-block-development -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install gambitph/Stackable wp-block-development --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/wp-block-development .agents/skills/wp-block-development && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "wp-block-development" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-block-development into .agents/skills/wp-block-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-block-development", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add gambitph/Stackable --skill wp-block-development -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install gambitph/Stackable wp-block-development --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/wp-block-development .cursor/skills/wp-block-development && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "wp-block-development" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-block-development into .cursor/skills/wp-block-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-block-development", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/gambitph/Stackable.git --path .cursor/skills/wp-block-development

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add gambitph/Stackable --skill wp-block-development -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install gambitph/Stackable wp-block-development --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/wp-block-development .gemini/skills/wp-block-development && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "wp-block-development" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-block-development into .gemini/skills/wp-block-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-block-development", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install gambitph/Stackable wp-block-development

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add gambitph/Stackable --skill wp-block-development -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/wp-block-development .github/skills/wp-block-development && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "wp-block-development" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-block-development into .github/skills/wp-block-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-block-development", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add gambitph/Stackable --skill wp-block-development -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install gambitph/Stackable wp-block-development --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/wp-block-development .opencode/skills/wp-block-development && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "wp-block-development" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-block-development into .opencode/skills/wp-block-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-block-development", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: wp-block-development
GitHub stars: 350
Used in: 3 other repos
Token cost: ~1.6k tokens
SKILL.md length: 703 words
Files: 12 (incl. scripts, references)
Skills in repo: 18
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: GPL-3.0

At a glance

A skill your agent uses when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering…

Works in 11 steps: Triage and locate blocks → Create a new block (if needed) → Ensure apiVersion 3 (WordPress 6.9+) → …
Developing WordPress (Gutenberg) blocks: block.json metadata
SKILL.md covers When to use, Inputs required, Procedure and Verification, plus 2 more sections
Runs JavaScript scripts from its folder; calls node

What it does

Wp Block Development is an agent skill from gambitph/Stackable. Use when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering (render.php/rendercallback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts and reference files (for example `references/attributes-and-serialization.md`, `references/block-json.md` and `references/creating-new-blocks.md`). Compatibility notes: Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

It works with WordPress and PHP. The repository describes itself as: Page Builder Blocks for WordPress. An Amazing Block Library for the new WordPress Block Editor (Gutenberg). The licence is GPL-3.0.

When your agent uses it

Developing WordPress (Gutenberg) blocks: block.json metadata
Registerblocktype(frommetadata)
Attributes/serialization
Dynamic rendering (render.php/rendercallback)

Example prompts

“/wp-block-development”

Requirements

Node.js
Compatibility (from SKILL.md): Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

Workflow steps

11 steps, taken from the step headings in SKILL.md.

Triage and locate blocks
Create a new block (if needed)
Ensure apiVersion 3 (WordPress 6.9+)
Pick the right block model
Update block.json safely
Register the block (server-side preferred)
Implement edit/save/render patterns
Inner blocks (block composition)
Attributes and serialization
Migrations and deprecations (avoid "Invalid block")
Tooling and verification commands

What it can do on your machine

Read from SKILL.md and the folder at commit 5c13d80. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.
From compatibility in the SKILL.md frontmatter.

Context cost

Wp Block Development loads about 1.6k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 703 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~86
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~4.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from gambitph/Stackable at commit 5c13d80, republished under its GPL-3.0 licence (© gambitph). 703 words, ~1,615 tokens.

Download SKILL.mdSave it as .claude/skills/wp-block-development/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.

name: wp-block-development
description: Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.
compatibility: Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

WP Block Development

When to use

Use this skill for block work such as:

creating a new block, or updating an existing one
changing block.json (scripts/styles/supports/attributes/render/viewScriptModule)
fixing “block invalid / not saving / attributes not persisting”
adding dynamic rendering (render.php / render_callback)
block deprecations and migrations (deprecated versions)
build tooling for blocks (@wordpress/scripts, @wordpress/create-block, wp-env)

Inputs required

Repo root and target (plugin vs theme vs full site).
The block name/namespace and where it lives (path to block.json if known).
Target WordPress version range (especially if using modules / viewScriptModule).

Procedure

0) Triage and locate blocks

Run triage:
- node skills/wp-project-triage/scripts/detect_wp_project.mjs
List blocks (deterministic scan):
- node skills/wp-block-development/scripts/list_blocks.mjs
Identify the block root (directory containing block.json) you’re changing.

If this repo is a full site (wp-content/ present), be explicit about which plugin/theme contains the block.

1) Create a new block (if needed)

If you are creating a new block, prefer scaffolding rather than hand-rolling structure:

Use @wordpress/create-block to scaffold a modern block/plugin setup.
If you need Interactivity API from day 1, use the interactive template.

Read:

references/creating-new-blocks.md

After scaffolding:

Re-run the block list script and confirm the new block root.
Continue with the remaining steps (model choice, metadata, registration, serialization).

2) Ensure apiVersion 3 (WordPress 6.9+)

WordPress 6.9 enforces apiVersion: 3 in the block.json schema. Blocks with apiVersion 2 or lower trigger console warnings when SCRIPT_DEBUG is enabled.

Why this matters:

WordPress 7.0 will run the post editor in an iframe regardless of block apiVersion.
apiVersion 3 ensures your block works correctly inside the iframed editor (style isolation, viewport units, media queries).

Migration: Changing from version 2 to 3 is usually as simple as updating the apiVersion field in block.json. However:

Test in a local environment with the iframe editor enabled.
Ensure any style handles are included in block.json (styles missing from the iframe won't apply).
Third-party scripts attached to a specific window may have scoping issues.

Read:

references/block-json.md (apiVersion and schema details)

3) Pick the right block model

Static block (markup saved into post content): implement save(); keep attributes serialization stable.
Dynamic block (server-rendered): use render in block.json (or render_callback in PHP) and keep save() minimal or null.
Interactive frontend behavior:
- Prefer viewScriptModule for modern module-based view scripts where supported.
- If you're working primarily on data-wp-* directives or stores, also use wp-interactivity-api.

4) Update `block.json` safely

Make changes in the block’s block.json, then confirm registration matches metadata.

For field-by-field guidance, read:

references/block-json.md

Common pitfalls:

changing name breaks compatibility (treat it as stable API)
changing saved markup without adding deprecated causes “Invalid block”
adding attributes without defining source/serialization correctly causes “attribute not saving”

Show full SKILL.md (273 more words)Show less

5) Register the block (server-side preferred)

Prefer PHP registration using metadata, especially when:

you need dynamic rendering
you need translations (wp_set_script_translations)
you need conditional asset loading

Read and apply:

references/registration.md

6) Implement edit/save/render patterns

Follow wrapper attribute best practices:

Editor: useBlockProps()
Static save: useBlockProps.save()
Dynamic render (PHP): get_block_wrapper_attributes()

Read:

references/supports-and-wrappers.md
references/dynamic-rendering.md (if dynamic)

7) Inner blocks (block composition)

If your block is a “container” that nests other blocks, treat Inner Blocks as a first-class feature:

Use useInnerBlocksProps() to integrate inner blocks with wrapper props.
Keep migrations in mind if you change inner markup.

Read:

references/inner-blocks.md

8) Attributes and serialization

Before changing attributes:

confirm where the attribute value lives (comment delimiter vs HTML vs context)
avoid the deprecated meta attribute source

Read:

references/attributes-and-serialization.md

9) Migrations and deprecations (avoid "Invalid block")

If you change saved markup or attributes:

Add a deprecated entry (newest → oldest).
Provide save for old versions and an optional migrate to normalize attributes.

Read:

references/deprecations.md

10) Tooling and verification commands

Prefer whatever the repo already uses:

@wordpress/scripts (common) → run existing npm scripts
wp-env (common) → use for local WP + E2E

Read:

references/tooling-and-testing.md

Verification

Block appears in inserter and inserts successfully.
Saving + reloading does not create “Invalid block”.
Frontend output matches expectations (static: saved markup; dynamic: server output).
Assets load where expected (editor vs frontend).
Run the repo’s lint/build/tests that triage recommends.

Failure modes / debugging

If something fails, start here:

references/debugging.md (common failures + fastest checks)
references/attributes-and-serialization.md (attributes not saving)
references/deprecations.md (invalid block after change)

Escalation

If you’re uncertain about upstream behavior/version support, consult canonical docs first:

WordPress Developer Resources (Block Editor Handbook, Theme Handbook, Plugin Handbook)
Gutenberg repo docs for bleeding-edge behaviors

Files

SKILL.md and 11 other files (scripts, references) in .cursor/skills/wp-block-development of gambitph/Stackable.

SKILL.md
references/attributes-and-serialization.md
references/block-json.md
references/creating-new-blocks.md
references/debugging.md
references/deprecations.md
references/dynamic-rendering.md
references/inner-blocks.md
references/registration.md
references/supports-and-wrappers.md
references/tooling-and-testing.md
scripts/list_blocks.mjs

Open the folder on GitHubat commit 5c13d80

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in gambitph/Stackable, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Wp Block Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Wp Block Development compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Wp Block Development this skillgambitph/Stackable	350	3 repos	~1.6k	Automated safety check: Pass	GPL-3.0	today
WooCommerce Code Reviewwoocommerce/woocommerce	11k	3 repos	~1.1k	Automated safety check: Pass	Custom licence	today
Wp Performance Reviewelvismdev/claude-wordpress-skills	234	1 repos	~4.5k	Automated safety check: Pass	MIT	10 mo ago
Wp Interactivity APIAutomattic/agent-skills	211	2 repos	~1.5k	Automated safety check: Pass	None	8 mo ago
WooCommerce Email Editor Developmentwoocommerce/woocommerce	11k	—	~893	Automated safety check: Pass	Custom licence	today
WooCommerce Dev Cyclewoocommerce/woocommerce	11k	3 repos	~431	Automated safety check: Pass	Custom licence	today

Similar skills

WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
11k GitHub starsUsed in 3 repos~1.1k tokens
DevelopmentAuto-check passed
Wp Performance Review
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
234 GitHub starsUsed in 1 repo~4.5k tokens
Business, Finance & HRAuto-check passed
Wp Interactivity API
Automattic/agent-skills
A skill your agent uses when building or debugging WordPress Interactivity API features (data-wp- directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration…
211 GitHub starsUsed in 2 repos~1.5k tokens
DevelopmentAuto-check passed
WooCommerce Email Editor Development
woocommerce/woocommerce
Sets up a local environment for the WooCommerce block email editor, with a watcher, Mailpit email capture and build and test commands for its PHP and JS packages.
11k GitHub stars~893 tokensUpdated today
Backend & APIsAuto-check passed
WooCommerce Dev Cycle
woocommerce/woocommerce
Workflow for WooCommerce development: run PHP and JavaScript tests, lint and fix code style on the current branch, and follow guides for i18n and markdown.
11k GitHub starsUsed in 3 repos~431 tokens
DevelopmentAuto-check passed
Blueprint
bonny/WordPress-Simple-History
A skill your agent uses when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources…
317 GitHub starsUsed in 1 repo~4k tokens
DevelopmentAuto-check passed

More from gambitph/Stackable

All 18 skills in this repo

Wp Block Themes
gambitph/Stackable
A skill your agent uses when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style…
350 GitHub starsUsed in 3 repos~985 tokens
Auto-check passed
Wp Performance
gambitph/Stackable
A skill your agent uses when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers)…
350 GitHub starsUsed in 3 repos~1.5k tokens
Auto-check passed
Wp Plugin Development
gambitph/Stackable
A skill your agent uses when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security…
350 GitHub starsUsed in 3 repos~999 tokens
Auto-check passed
Wp Project Triage
gambitph/Stackable
A skill your agent uses when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a…
350 GitHub starsUsed in 3 repos~371 tokens
Auto-check passed
Wp Plugin Directory Guidelines
gambitph/Stackable
A skill your agent uses when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or…
350 GitHub starsUsed in 1 repo~1.6k tokens
Auto-check passed
Add Changelog
gambitph/Stackable
Adds or updates a WordPress plugin changelog entry in readme.txt from the project's Release Roadmap for a confirmed plugin version.
350 GitHub stars~1.5k tokensUpdated today
Auto-check passed

Works with

Questions about Wp Block Development

What does Wp Block Development do?

A skill your agent uses when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering…. Wp Block Development is an agent skill from gambitph/Stackable.php/rendercallback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.

When should I use Wp Block Development?

Wp Block Development fits situations like: developing WordPress (Gutenberg) blocks: block.json metadata; registerblocktype(frommetadata); attributes/serialization; dynamic rendering (render.php/rendercallback).

How do I install Wp Block Development in Claude Code?

Run `npx skills add gambitph/Stackable --skill wp-block-development -a claude-code`. Or copy the skill folder (.cursor/skills/wp-block-development in gambitph/Stackable) into .claude/skills/wp-block-development in your project. Claude Code loads it when a task matches its description.

How do I install Wp Block Development in Codex?

Run `npx skills add gambitph/Stackable --skill wp-block-development -a codex`. Or copy the skill folder (.cursor/skills/wp-block-development in gambitph/Stackable) into .agents/skills/wp-block-development in your project. Codex loads it when a task matches its description.

Can I use Wp Block Development in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gambitph/Stackable --skill wp-block-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wp-block-development, .gemini/skills/wp-block-development, .github/skills/wp-block-development and .opencode/skills/wp-block-development in your project.

What does Wp Block Development need to run?

Going by SKILL.md and its folder, Wp Block Development needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js. Compatibility (from SKILL.md): Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI..

Does Wp Block Development access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Wp Block Development safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Wp Block Development use?

Wp Block Development is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wp Block Development use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.

What are the alternatives to Wp Block Development?

Skills that share tags, products or a category with Wp Block Development: WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Wp Performance Review (elvismdev/claude-wordpress-skills, 234 stars), Wp Interactivity API (Automattic/agent-skills, 211 stars) and WooCommerce Email Editor Development (woocommerce/woocommerce, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wp Block Development?

gambitph (a GitHub organization) maintains it in gambitph/Stackable, which has 350 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: gambitph/Stackable on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Wp Block Development

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

WP Block Development

When to use

Inputs required

Procedure

0) Triage and locate blocks

1) Create a new block (if needed)

2) Ensure apiVersion 3 (WordPress 6.9+)

3) Pick the right block model

4) Update block.json safely

5) Register the block (server-side preferred)

6) Implement edit/save/render patterns

7) Inner blocks (block composition)

8) Attributes and serialization

9) Migrations and deprecations (avoid "Invalid block")

10) Tooling and verification commands

Verification

Failure modes / debugging

Escalation

Files

Used in 3 other repositories

Compare with similar skills

Similar skills

More from gambitph/Stackable

Related

Questions about Wp Block Development

4) Update `block.json` safely