Last month I wrote about how Claude changed everything for me with custom Gutenberg blocks. I thought I had reached peak workflow. Cursor + Claude, my `.cursor/rules` file, my master prompt template. I was shipping blocks in 15 minutes instead of 6 hours.
Then WordPress itself dropped something that made half of my “secret sauce” obsolete — in the best possible way.
Enter: Agent Skills for WordPress
The WordPress project quietly released an official repo called [agent-skills](https://github.com/WordPress/agent-skills). The tagline says it all:
“Teach AI coding assistants how to build WordPress the right way.”
Agent Skills are portable bundles of instructions, checklists, and scripts that AI assistants — Claude, Copilot, Codex, Cursor, whatever you use — read *before* they touch your WordPress code. Instead of the model guessing from its training data (which is often 2 years out of date), it follows documented, contributor-reviewed procedures.
If you read my last post, you’ll remember my Step 1 was writing my own rules file: “Always use apiVersion 3, prefer render.php, follow WordPress Coding Standards, proper escaping and i18n…”
That’s exactly what these skills are. Except written from official Gutenberg and WordPress documentation, reviewed by WordPress contributors, and way, way more thorough than my little rules file.
Why This Matters (The Problem Nobody Talks About)
AI assistants are amazing, but if you’ve done serious WordPress work with them, you’ve hit these walls:
1. Outdated patterns. Ask for a theme and you might get a classic PHP theme when you wanted a block theme with `theme.json`. Ask for a block and sometimes you get apiVersion 2 or — the horror — a shortcode.
2. Missing security. Escaping, sanitization, nonces, capability checks. The AI *knows* about them but doesn’t always apply them unless you nag.
3. The dreaded “Invalid block” error. If you’ve ever changed a block’s markup and broken every existing instance on a client’s site because you skipped deprecations… you know the pain. This one has bitten me twice.
4. Ignoring your existing tooling. The AI happily reinvents your build setup instead of using what’s already in the repo.
Agent Skills solve all four. There’s literally a skill dedicated to block deprecations.
What’s in the Box
The repo currently ships 15 skills. Some highlights:
– wp-block-development — everything I was manually prompting for: `block.json`, attributes, rendering, and yes, deprecations
– wp-block-themes — `theme.json`, templates, patterns, style variations
– wp-plugin-development — plugin architecture, hooks, Settings API, security
– wp-interactivity-api — remember in my last post when I told Claude “make the carousel use the new Interactivity API”? Now there’s a whole skill teaching it the `data-wp-*` directives properly
– wp-rest-api, wp-performance, wp-wpcli-and-ops, wp-phpstan, wp-playground, and more
There’s even a wordpress-router skill that classifies your repo and routes the AI to the right workflow, and wp-project-triage that auto-detects your project type, tooling, and versions. So the AI stops assuming and starts checking.
Installing It (Took Me 3 Minutes)
I installed globally so every project gets the skills:
git clone https://github.com/WordPress/agent-skills.git
cd agent-skills
shared/scripts/skillpack-build.mjs --clean
shared/scripts/skillpack-install.mjs --global
That drops everything into `~/.claude/skills/` where Claude Code auto-discovers them. Cursor users, there’s a `–targets=cursor-global` option that installs to `~/.cursor/skills/`.
For client repos, you can install per-project and even pick specific skills:
node shared/scripts/skillpack-install.mjs --dest=../client-site --targets=claude,cursor --skills=wp-block-development,wp-block-themes
It supports Codex and VS Code / GitHub Copilot targets too. Whatever your assistant, it’s covered.
The Before/After Test
I did an experiment. Same prompt, same model, two fresh plugin folders — one with skills installed, one without.
The prompt: “Create a native Gutenberg block called Team Grid. 2–4 columns, photo, name, role, social links. Then change the markup structure of the name field.”
Without skills: Great block (Claude is still Claude). But when I asked for the markup change, it just… changed it. Any existing instance would have thrown “Invalid block” in the editor.
With skills: It generated the block, and when I asked for the markup change, it *automatically wrote a deprecation entry* with the old save function and a migration. Unprompted. It also ran through a verification checklist at the end — escaping, i18n, accessibility — like a senior dev reviewing its own PR.
That deprecation thing alone would have saved me an embarrassing client call back in May.
My Updated Workflow (June ? July 2026)
So here’s what changed from last month’s post:
1. Write my own `.cursor/rules` with WordPress standards ? Install agent-skills once, globally
2. Master prompt template? still useful, but now shorter. I describe the “what”, the skills handle the “how”.
3. Iterate in chat? unchanged, still magic
My prompts have gotten lazier and my output has gotten better. That’s the dream, right?
Honest Limitations (Again, Not Selling You Anything)
– It’s v1. The skills were AI-generated from official docs, then reviewed and edited by WordPress contributors, and they’re upfront about that. Expect rough edges and improvements over time.
– It targets WordPress 6.9+ — if you’re maintaining older client sites, the guidance may not always fit.
– You still need to test in a real WordPress environment. Skills make the AI dramatically more reliable, not infallible.
– And you still need to understand WordPress basics. This is still “super-code,” not “no-code.”
The Bigger Picture
What excites me most isn’t even the skills themselves. It’s that **WordPress, the project, is officially treating AI assistants as first-class citizens of the ecosystem**. The repo is GPL, community contributions are welcome, and most skills are just Markdown — you don’t need to be a coding wizard to improve them. If you’ve got hard-won WordPress expertise, this is a genuinely great way to give back.
Last month I said Claude changed what a solo developer can ship. This month, WordPress made sure your AI ships it the right way.
Go install it. Your future self — the one who doesn’t get the “Invalid block” support email — will thank you.
Enjoy (properly skilled) vibe coding!