How to build and run a WordPress site with an AI agent

1. 1

   Install the WordPress set for the build

   npx skills add WordPress/agent-skills --skill wp-plugin-development --yes, swapping the skill for wp-block-development, wp-block-themes or wp-rest-api as the work demands. wordpress-router picks the right one for a repo if you would rather not choose.

2. 2

   Let it correct the patterns an agent gets wrong

   The set exists for specific, repeated failures: blocks written without deprecations, which produce "Invalid block" errors for every existing post; themes written pre-block-theme; plugin code that skips the settings API and the security conventions around it.

3. 3

   Stand the site up on a host

   Hostinger’s hosting skill creates the website and installs WordPress; migrate-to-hosting imports an existing one from an archive and a database dump. This is where the WordPress set stops and a host’s begins.

4. 4

   Check before you update, not after

   maintain-wordpress reads core, plugin and theme versions with their known vulnerabilities and reports what needs doing — including which vulnerable plugins have no fix and should be uninstalled — before changing anything.

5. 5

   Update one site at a time and prove each still loads

   That is the order the skill enforces, and it is the right one: updates are queued jobs, so a success response means queued rather than done. Poll until the change shows, confirm the site still loads, then move to the next.

The repository says it plainly: AI assistants generate outdated WordPress patterns, miss security considerations in plugin development, and skip block deprecations in a way that produces "Invalid block" errors. Those are not general coding mistakes, they are WordPress-specific ones that a model trained on a decade of pre-Gutenberg tutorials makes by default.

It is worth knowing how the set was built, because the project discloses it rather than hiding it: the skills were generated with a model from the official Gutenberg and WordPress documentation, then reviewed and edited by WordPress contributors, and the repository links its own AI authorship note. That is a more honest provenance statement than most first-party skill sets make, and it is the reason to treat this as v1 rather than gospel.

Building WordPress with an agent now has a first-party answer. Running one does not, beyond a single host: the maintenance, vulnerability and audit skills in this catalogue are Hostinger’s, and they reach Hostinger-hosted sites only. If your site is elsewhere, the update path is still wp-admin or WP-CLI by hand.

That is a real gap rather than a ranking. WordPress runs a large share of the web on hosts that have published nothing, and an agent cannot patch what it cannot reach. When another host ships an equivalent set it will be catalogued here and this paragraph will change.