Choose official WordPress agent skills for your website project Print

Quick answer

Start with wordpress-router and wp-project-triage from the WordPress project's agent-skills repository, then add the skill for the requested task. Keep the selection small and verify that the instructions match your WordPress version, editor and development environment.

Applies to

Customers using an AI coding assistant for an Interactive Online WordPress website. The WordPress-maintained collection supplies development instructions and helper files; it does not log in to WordPress or enable a remote editing service. Its current README targets WordPress 7.0 and newer. For an older site, review compatibility and use its supported APIs; a skill's version target is not a reason to run an unplanned production upgrade.

Choose by the work you need

• Identify the project: wordpress-router and wp-project-triage.
• Custom plugin behavior: wp-plugin-development. For custom REST endpoints, add wp-rest-api.
• Block editor components: wp-block-development; use wp-block-themes for block themes and their templates.
• Hosting and maintenance commands: wp-wpcli-and-ops. For investigating slow backend behavior, use wp-performance.
• AI-accessible WordPress actions: wp-abilities-api, with the audit and verification skills when reviewing an implementation. Skills do not turn an unreviewed endpoint into a permission-safe connector.
• Local experiments: wp-playground and blueprint. A disposable preview does not establish compatibility with the production server's extensions or integrations.

1. Install selected skills

1. Review the WordPress repository's current README, relevant skill folders, compatibility policy and GPL-2.0-or-later license.
2. Use its documented installation method. The command below lists choices; it downloads and executes a third-party installer, so review the installer source and use your local project rather than the hosting webroot.

npx skills add WordPress/agent-skills --list

To select just the two starting skills, the repository documents this command pattern:

npx skills add WordPress/agent-skills --skill wordpress-router wp-project-triage

3. Choose the intended assistant and project scope in the installer's prompts. Inspect the proposed destinations and preserve existing modified copies. Avoid installing the whole collection merely to make one page change.
4. Confirm discovery in the current client. Current Codex documentation describes .agents/skills, while some WordPress packaging instructions still show .codex/skills. If the installer uses an older layout, follow the current client's supported discovery path and retain complete referenced files. Do not create multiple discoverable copies to work around a missing skill.
5. When using the repository's build/install scripts instead, review their packaging instructions first. Some skills depend on shared helpers, so copying only SKILL.md can produce an incomplete installation.

2. Run a read-only project assessment

Use wordpress-router and wp-project-triage for this local site.
Identify the WordPress version, active theme, page builder,
affected page and available verification commands.
I need to change the About page introduction only.
Recommend the smallest workflow and explain what access it needs.
Do not change files, update WordPress, or connect to production.

Compare the report with the site's actual theme and plugin inventory. Then install the one task-specific skill it needs, read its referenced guidance, and ask for a bounded plan. For a builder page, preserve native builder data and editability instead of recreating the page as a large HTML block.

Verify success and handle failures

Check that the assistant loaded the named skills from the intended locations, identified the correct site and editor, and proposed checks that your project can run. For an approved change, inspect the diff, reopen the native editor and test the affected customer task. If helper scripts fail, check required files and runtime versions. If a tool is unavailable, use a supported manual workflow or ask for help instead of granting broader account access.

When to contact support

Contact Interactive Online when the hosting account, WordPress installation, document root or available access method is unclear. Provide the affected page URL, tool and plugin versions, time and time zone, and the exact redacted error. Exclude passwords, Application Passwords, keys, tokens, cookies and customer records. Skill publishers handle their own installation defects and feature requirements; AI subscriptions, paid builders and connector licenses are separate from hosting.

Related help

• Skill installation, discovery and scope
• When WordPress Pro fits the task
• Review and publish a WordPress coding change
• WordPress REST and connector access
• Identify the page editor

Documentation and downloads

• WordPress agent-skills repository and installation
• WordPress skill packaging and shared files
• WordPress skill compatibility policy
• Current Codex discovery locations

Documentation and source review by Interactive Online: November 2, 2026. Installation sources and instructions were reviewed. A new installation or connected editing test was not performed for this article; confirm the versions, tools and permissions available in your own environment.