skilld
All skills
automattic avatar

/wordpress-router

@95e374f official
by automatticautomattic/agent-skills211 stars
37

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/automattic/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. ≈683 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 warning17d4 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    The skill is a WordPress project router designed to classify codebases and delegate tasks to specialized workflows. It follows standard development practices and uses internal scripts for project detection.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer7mo

    2/2 files flagged

Provenance

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

Last checked against GitHub 5 months ago.

Dormantupdated 9 months ago

Capability

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

Topics

  • wordpress
  • routing
  • triage
  • plugin
  • theme
  • gutenberg
  • wp-cli
  • php
  • classification

README badge

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

What it does

Classifies WordPress codebases (plugins, themes, block themes, Gutenberg blocks, or core) by running a triage script, then routes to the appropriate workflow skill based on project type and user intent. Helps agents avoid applying the wrong practices to the wrong codebase kind.

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 operates on the filesystem using bash and Node, with some workflows requiring WP-CLI.
What kinds of WordPress projects can this skill classify?
Plugins, themes, block themes, Gutenberg blocks, and WordPress core checkouts. The triage script identifies the project kind and recommends the right workflow based on that classification.
Do I need to run this skill first before other WordPress workflows?
Yes. This skill is designed to be used at the start of most WordPress tasks to identify the codebase type and route to the correct domain skill or workflow.
What happens if the triage script can't identify the project type?
If triage reports `kind: unknown`, the skill guides you to manually inspect composer.json, package.json, style.css, block.json, theme.json, or wp-content/ to clarify the project structure.

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