wordpress router
- Repo stars 1,627
- Author repo agent-skills
- Domain
- Security
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @WordPress · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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?”
Sections and files
Listed in source order.
sections -> When to use → Inputs required → Procedure → Verification → Failure modes / debugging → Escalation
terms -> - Repo root (current working directory). · 1. Run the project triage script: - node skills/wp-project-triage/scripts/detectwpproject.mjs 2. · - Re-run the triage script if you create or restructure significant files. · - If triage reports kind: unknown, inspect: - root composer.json, package.json, style.css, block.json, theme.json, wp-content/.
files/cmd -> node skills/wp-project-triage/scripts/detect_wp_project.mjs · skills/wordpress-router/references/decision-tree.md · kind: unknown · composer.json · package.json · style.css · block.json · theme.json
body sha256 -> b41cfd7c2e89
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
Run the project triage script:
node skills/wp-project-triage/scripts/detect_wp_project.mjsRead the triage output and classify: primary project kind(s), tooling available (PHP/Composer, Node, @wordpress/scripts),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: rootcomposer.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.