WP Plugin Development
94TrustedShips scriptsWordPress plugin architecture, security protocols, and lifecycle management.
What it does
Wp Plugin Development equips an assistant to handle the specific constraints of the WordPress ecosystem. It shifts the AI from generic coding advice to pattern-based development that aligns with official WordPress standards for hooks, admin interfaces, and data handling.
The skill provides guidance on setting up plugin bootstrap files, managing activation and uninstallation routines, and implementing secure settings pages. It acts as an architectural guide, ensuring that code structure remains maintainable and that security practices like input sanitization and capability checks are applied consistently.
When it earns its place
Reach for it when…
Apply this when building new features or refactoring existing logic within a WordPress plugin. It is the correct choice for tasks involving the Settings API, scheduling background tasks via WP-Cron, managing custom database tables, or performing security audits on form processing and data storage.
Look elsewhere when…
Do not rely on this skill for theme-level development or general PHP framework construction outside of WordPress. It is not designed for debugging server-level infrastructure, such as database optimization, PHP configuration, or web server tuning, which require different expertise.
What to say to use it
You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.
- create a new plugin settings page using the settings api
- how do I properly handle plugin activation and uninstallation
- add an admin settings menu to my existing plugin
- secure my plugin form inputs and database queries
Install it
Install for all your projects
Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.
git clone --depth 1 --branch trunk https://github.com/WordPress/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/wp-plugin-development ~/.claude/skills/wp-plugin-developmentInstall for one project only
Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.
cp -r /tmp/agent-skills/skills/wp-plugin-development .claude/skills/wp-plugin-developmentIf a skill of the same name exists in both places, the personal one wins.
Installing on Claude.ai or through the API instead? The full guide covers every surface.
Pair it with an MCP server
WP Plugin Development changes how the work is done. These servers change what Claude can reach while doing it.
- GitHub MCP Server53The skill sets the conventions the code should follow; GitHub MCP Server is what lets Claude read the repository it is writing into.
- Context Forge MCP Server86Context Forge MCP Server gives the code somewhere to actually run, so the skill's guidance can be checked instead of assumed.
- Supabase MCP Server100Pair with Supabase MCP Server when the code being written has to match a real schema rather than a described one.