Wordpress Router

Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).

211 stars 37 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Automattic/agent-skills --skill wordpress-router
Manual install
git clone --depth 1 https://github.com/Automattic/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/wordpress-router ~/.claude/skills/wordpress-router

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# WordPress Router

## When to use

Use this skill at the start of most WordPress tasks to:

- identify what kind of WordPress codebase this is (plugin vs theme vs block theme vs WP core checkout vs full site),
- pick the right workflow and guardrails,
- delegate to the most relevant domain skill(s).

## Inputs required

- Repo root (current working directory).
- The user’s intent (what they want changed) and any constraints (WP version targets, WP.com specifics, release requirements).

## Procedure

1. Run the project triage script:
   - `node skills/wp-project-triage/scripts/detect_wp_project.mjs`
2. Read the triage output and classify:
   - primary project kind(s),
   - tooling available (PHP/Composer, Node, @wordpress/scripts),
   - tests present (PHPUnit, Playwright, wp-env),
   - any version hints.
3. Route to domain workflows based on user intent + repo kind:
   - For the decision tree, read: `skills/wordpress-router/references/decision-tree.md`.
4. Apply guardrails before making changes:
   - Confirm any version constraints if unclear.
   - Prefer the repo’s existing tooling and conventions for builds/tests.

## Verification

- Re-run the triage script if you create or restructure significant files.
- Run the repo’s lint/test/build commands that the triage output recommends (if available).

## Failure modes / debugging

- If triage reports `kind: unknown`, inspect:
  - root `composer.json`, `package.json`, `style.css`, `block.json`, `theme.json`, `wp-content/`.
Read the full skill on GitHub

Details

Skill name
wordpress-router
Path
skills/wordpress-router/SKILL.md
Repo updated
1 February 2026

FAQ

What does the Wordpress Router skill do?

Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).

How do I install the Wordpress Router skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Automattic/agent-skills --skill wordpress-router. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Wordpress Router popular?

It lives in Automattic/agent-skills, which has 211 GitHub stars and 37 forks.

Related skills

Wp Abilities API

211

Automattic/agent-skills

Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.

Software Development37

Wp Block Development

211

Automattic/agent-skills

Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.

Software Development37

Wp Block Themes

211

Automattic/agent-skills

Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).

Frontend & Design37

Multica Artifact Frontend

279

it235/multica-best-practices

Frontend artifact sync—push the frontend deliverable set (page/component/state/style) and run-url to Multica frontend-artifact (product-requirement mapping); the preferred mount for @FrontendDev.

Frontend & Design33

Vlmkit

423

mizchi/skills

Verify frontend changes with @mizchi/vlmkit: compare rendered HTML or screenshots, manage visual baselines, and inspect layout, accessibility or interaction defects. Use after visible UI changes or for a requested visual audit. Choose deterministic checks first, then use model-assisted modes when the task requires them.

Frontend & Design

Multica Artifact Frontend

279

it235/multica-best-practices

前端产物薄编排:实现说明文档规范,落地调 multica-platform-confluence + multica-platform-jira。用于 @FrontendDev 发布交互/页面对照说明。

Frontend & Design33

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.