# 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.

- Skill: `automattic/wordpress-creator-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add automattic/wordpress-creator-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/automattic/wordpress-creator-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: Automattic (https://skillmd.com/u/automattic)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/automattic/wordpress-creator-2

---


# 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.