skilld
All skills
wordpress avatar

/wordpress-router

@20324d2 official
by wordpresswordpress/agent-skills2.2k stars
327

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

Ask your Agent

Use this Skill: https://skilld.dev/gh/wordpress/agent-skills/wordpress-router

This session only. Nothing lands on disk.

SKILL.md

≈77 tokens always: the name and description. ≈441 when used: this file. ≈789 more on demand in 1 file.

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/.
  • If the repo is huge, consider narrowing scanning scope or adding ignore rules to the triage script.

Escalation

  • If routing is ambiguous, ask one question:
    • “Is this intended to be a WordPress plugin, a theme (classic/block), or a full site repo?”

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill is a router for WordPress-related development tasks, designed to classify repositories and delegate to relevant domain workflows based on the detected project type. No security issues were detected.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    2/2 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 20324d2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 3 months ago

Capability

Other metadata
compatibility
Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

Topics

  • wordpress
  • routing
  • classification
  • plugin
  • theme
  • gutenberg
  • wp-cli
  • php
  • project-detection

README badge

README badge for wordpress/agent-skills/wordpress-router

What it does

Classifies WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core) and routes to the appropriate workflow using filesystem detection and a decision tree. Runs a triage script to identify project kind, available tooling, and test setup, then delegates to domain-specific skills for blocks, theme.json, REST API, WP-CLI, performance, security, testing, or release packaging.

Generated from the current SKILL.md.

Frequently asked

What WordPress versions does this skill support?
WordPress 6.9+ with PHP 7.2.24+. The skill uses filesystem detection and bash/node scripts, with some workflows requiring WP-CLI.
What project types can this skill classify?
Plugins, themes, block themes, Gutenberg blocks, WP core checkouts, and full site repos. It identifies the project kind and recommends the appropriate workflow.
Does this skill make changes to the codebase?
No. This skill runs triage and routing logic to classify the repo and delegate to other domain skills. It does not modify files directly.
What happens if the triage script cannot identify the project type?
The skill will report `kind: unknown` and suggest manually inspecting composer.json, package.json, style.css, block.json, theme.json, or wp-content/ to determine the project structure.

Generated from the current SKILL.md. These answers refresh after source changes.