What it does
Verify a WordPress plugin's Abilities API registrations: enumerate abilities, check that callback behavior matches each annotation's claim (the adversarial readonly-but-writes detection), validate permissions and schemas, and validate audit documents produced by wp-abilities-audit.
Install
This skill ships in WordPress/agent-skills (Official, WordPress core fundamentals).
One command installs it for any assistant. Run this from your project root:
npx skills add WordPress/agent-skills --skill wp-abilities-verifyYou'll be asked to choose a scope: project (shared with your team, committed to version control) or global (available across all your projects). Add --global to skip the prompt and install globally.
Use it in your AI assistant
The destination folder, and how the assistant discovers it, differs per tool:
Claude Code
.claude/skills/wp-abilities-verify/ (or ~/.claude/skills/wp-abilities-verify/ for all projects)
- Claude Code auto-discovers skills in .claude/skills/ (project) or ~/.claude/skills/ (global, every project).
- Claude reaches for the skill on its own when a task matches its description, or you can name it directly.
GitHub Copilot (VS Code)
.github/skills/wp-abilities-verify/
- The skill is copied into .github/skills/wp-abilities-verify/, where Copilot in VS Code picks it up.
- Copilot Chat applies it automatically once your task matches the skill's description.
OpenAI Codex
.codex/skills/wp-abilities-verify/
- This installs the skill to .codex/skills/wp-abilities-verify/, which Codex reads for standing instructions on matching tasks.
- Point Codex at it directly if needed: "follow .codex/skills/wp-abilities-verify/SKILL.md for this task."
Cursor
.cursor/skills/wp-abilities-verify/ (or ~/.cursor/skills/wp-abilities-verify/ globally)
- Cursor discovers skills in .cursor/skills/ (project) or ~/.cursor/skills/ (global).
- Cursor loads it automatically when a request matches, same as its native Rules.
Compatibility
Targets WordPress 7.0+ plugins (PHP 7.4.0+). Requires a runnable environment (wp-env, docker-based dev stack, or equivalent) for runtime mode; static mode runs entirely from the plugin checkout with no env. Filesystem-based agent with bash + node.