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.

referencesdecision-tree.md

≈789 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Router decision tree (v1)

This is a lightweight routing guide. It assumes you can run wp-project-triage first.

Step 1: classify repo kind (from triage)

Use triage.project.kind and the strongest signals:

  • wp-core → treat as WordPress core checkout work (core patches, PHPUnit, build tools).
  • wp-site → treat as a full site repo (wp-content present; changes might be theme + plugins).
  • wp-block-theme → theme.json/templates/patterns workflows.
  • wp-theme → classic theme workflows (templates PHP, functions.php, style.css).
  • wp-block-plugin → Gutenberg block development in a plugin (block.json, build pipeline).
  • wp-plugin / wp-mu-plugin → plugin workflows (hooks, admin, settings, cron, REST, security).
  • gutenberg → Gutenberg monorepo workflows (packages, tooling, docs).

If multiple kinds match, prefer the most specific: gutenberg > wp-core > wp-site > wp-block-theme > wp-block-plugin > wp-theme > wp-plugin.

Step 2: route by user intent (keywords)

Route by intent even if repo kind is broad (like wp-site):

  • Interactivity API / data-wp- directives / @wordpress/interactivity / viewScriptModule*
    • Route → wp-interactivity-api.
  • Abilities API / wp_register_ability / wp-abilities/v1 / @wordpress/abilities
    • Route → wp-abilities-api.
  • Ambiguous WordPress Playground requests
    • Route → wp-playground, then follow its routing wrapper.
  • Blueprint JSON / Blueprint schema / Blueprint steps / Blueprint bundles
    • Route → blueprint.
  • @wp-playground/cli / server / run-blueprint / build-snapshot / auto-mount / Xdebug
    • Route → wp-playground, then read references/cli.md or references/debugging.md.
  • playground.wordpress.net / Blueprint Editor / share links / browser-only Playground
    • Route → wp-playground, then read references/website.md.
  • Blocks / block.json / registerBlockType / attributes / save serialization
    • Route → wp-block-development.
  • theme.json / Global Styles / templates/*.html / patterns/
    • Route → wp-block-themes.
  • Plugins / hooks / activation hook / uninstall / Settings API / admin pages
    • Route → wp-plugin-development.
  • REST endpoint / register_rest_route / permission_callback
    • Route → wp-rest-api.
  • WP-CLI / wp-cli.yml / commands
    • Route → wp-wpcli-and-ops.
  • Build tooling / @wordpress/scripts / webpack / Vite / npm scripts
    • Route → wp-build-tooling (planned).
  • Testing / PHPUnit / wp-env / Playwright
    • Route → wp-testing (planned).
  • PHPStan / static analysis / phpstan.neon / phpstan-baseline.neon
    • Route → wp-phpstan.
  • Performance / caching / query profiling / editor slowness
    • Route → wp-performance.
  • Security / nonces / capabilities / sanitization/escaping / uploads
    • Route → wp-security (planned).

Step 3: guardrails checklist (always)

  • Verify detected tooling before suggesting commands (Composer vs npm/yarn/pnpm).
  • Prefer existing lint/test scripts if present.
  • If version constraints aren’t detectable, ask for target WP core and PHP versions.

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.