wordpress-creator

Route WordPress build and audit requests to the right implementation path for a Studio-backed site. Use when the user wants WordPress work and it is not yet clear whether the task should be handled as site creation, theme work, a custom block, a plugin, or an audit.

Jump to install

Repository: Automattic/build-with-wordpress
Last source activity: June 12, 2026 at 01:04
Detected SKILL.md language: English
Stars: 7
Forks: 2

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Automattic/build-with-wordpress --skill wordpress-creator

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

studio

Use WordPress Studio for local WordPress development, preferring MCP and falling back to the Studio CLI when needed.

2026-06-15

auditing

Audit a Studio-backed WordPress site for performance, accessibility, and visible frontend quality issues, then recommend or validate improvements.

2026-06-12

block-creator

Create, edit, build, and review a custom WordPress Gutenberg block plugin inside a Studio-backed site.

2026-06-12

View all from this repository

WordPress Creator

Use this skill as the top-level decision maker for WordPress implementation and audit work.

Ownership

This skill owns:

choosing between site-creator, theme-creator, block-creator, plugin-creator, and auditing

picking the smallest fitting WordPress abstraction

handing execution off to the specialist skill once the approach is clear

Routing rules

Use site-creator when the user wants a new site, homepage, landing page, or a full site built from a brief.

Use theme-creator when the main work is theme templates, layout, styling, presentation, or a visual redesign.

Use block-creator when the main deliverable is an editor-insertable content block that can't be achieved with existing core blocks or aleady installed custom blocks.

Use plugin-creator when the request is reusable site functionality, admin/settings UI, REST endpoints, scheduled tasks, integrations, or backend behavior that should survive theme changes, and that can't be achieved with an existing plugin.

Use auditing when the main request is performance review, accessibility review, frontend QA, or optimization guidance on an existing site.

If the request could fit more than one path, choose the smallest abstraction that cleanly solves it.

Guardrails

Do not reach for a plugin when a theme or block would solve the request more directly.

Do not reach for a plugin when an existing installed, or well known plugin is available. For example, Set up an ecommerce system could be accomplished with the WooCommerce plugin.

Do not route pure presentation work into plugin-creator.

Do not route reusable backend behavior into theme-creator.

Once the path is clear, rely on the specialist skill instead of restating its workflow here.