wordpress-router

Overview of wordpress-router skill

wordpress-router is a WordPress triage skill that helps an agent classify a repo fast and choose the right downstream workflow before making changes. It is most useful when the user’s request is broad or the codebase could be a plugin, classic theme, block theme, Gutenberg package, WordPress core checkout, or full site repo.

What this skill is for

The wordpress-router skill is for routing, not editing. Its job is to reduce early guesswork by identifying the repo kind, available tooling, likely tests, and the most relevant domain skill to use next.

Who should install it

Install wordpress-router if you regularly work in WordPress codebases and need an agent to decide whether to treat a repo as blocks, theme.json, REST, WP-CLI, security, testing, or release packaging work. It is especially useful for agent orchestration across mixed WordPress repositories.

Why it matters

Without a router, agents often jump into the wrong mental model: classic theme logic for a block theme, plugin assumptions for a site repo, or generic edits instead of the correct WordPress workflow. This skill adds a practical classification step that improves downstream prompt quality and lowers the chance of unnecessary changes.

How to Use wordpress-router skill

Install and locate the decision path

Use the documented install path for the wordpress-router skill, then start with SKILL.md. The repository also points to references/decision-tree.md, which is the most useful follow-up read for routing decisions.

Give the skill the right inputs

The wordpress-router skill works best when you provide:

• the repo root or current working directory,
• the user’s actual intent,
• version constraints such as WordPress targets or WP.com requirements,
• any hard limits on tooling, release process, or testing.

A weak request like “fix this WordPress repo” is harder to route well. A stronger request looks like: “This is a wp-content repo; determine whether we should treat it as a block theme or plugin workflow, then plan the safest path for a template change with existing tests.”

Suggested workflow for first use

1. Run the project triage step described in SKILL.md.
2. Read the triage output to determine project kind, tooling, and test coverage.
3. Open references/decision-tree.md to map intent to the next workflow.
4. Apply repository conventions before editing, especially existing build and test commands.

What to check first in the repo

For the wordpress-router guide, prioritize:

• SKILL.md for the routing procedure and guardrails,
• references/decision-tree.md for intent-based routing,
• any repo-specific docs only after you know the project kind.

That order matters because the skill is designed to narrow the path before you inspect everything else.

wordpress-router skill FAQ

Is wordpress-router a replacement for domain skills?

No. It is a front-end decision skill for Agent Orchestration. It helps choose the right WordPress workflow, but it does not replace a block, theme, plugin, or testing skill once the repo is classified.

When should I not use wordpress-router?

Skip it when the task is already narrow and obvious, such as a single known file edit in a clearly identified workflow. It is less valuable when there is no routing ambiguity.

Is wordpress-router install worth it for beginners?

Yes, if beginners are likely to work across multiple WordPress repo types. It gives a safer starting point than a generic prompt, but it still expects the user to provide intent and constraints clearly.

How is this better than a plain prompt?

A plain prompt may ask for a change; wordpress-router first asks what kind of WordPress system it is and what workflow should govern the change. That extra classification step is the main advantage of the wordpress-router skill.

How to Improve wordpress-router skill

Provide clearer intent, not just a task

The best inputs name the desired outcome and the repo context. For example, instead of “make it faster,” use “this is a WordPress plugin repo; determine whether performance work should follow plugin, REST, or block workflows, then suggest the safest starting path.”

Add constraints that affect routing

The skill performs better when you include WordPress version targets, release requirements, and tooling limits. These details help it decide whether the repo should be treated as core, site, theme, plugin, or Gutenberg-oriented work.

Watch for common failure modes

The most common problem is under-specified context. If the agent cannot tell whether it is dealing with a block theme, classic theme, plugin, or site repo, the next workflow may be wrong. Another failure mode is skipping the decision tree and jumping straight to edits.

Iterate after the first classification

After the first pass, ask the agent to restate:

• the repo kind,
• the likely downstream skill,
• the files it used to decide,
• the main uncertainty still open.

That makes wordpress-router more useful for Agent Orchestration because you can correct the route before code changes begin.