wordpress-router

Classify WordPress repositories and route tasks to domain workflows.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/javiercasares/cloudfest-wporgdownload --skill wordpress-router-javiercasares
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wordpress-router
Source: https://github.com/javiercasares/cloudfest-wporgdownload/tree/main/.claude/skills/wordpress-router
Command: npx skills add https://github.com/javiercasares/cloudfest-wporgdownload --skill wordpress-router-javiercasares

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams quickly identify what kind of WordPress codebase they are dealing with (plugin, theme, block theme, WP core checkout, or full site) and route tasks to the correct workflow.

Core Features & Use Cases

  • Repo kind detection: Determine whether a repository is a plugin, theme, block theme, core checkout, or full site.
  • Intent-driven routing: Route to the most relevant domain workflow (plugins, themes, REST API, WP-CLI, etc.) based on user intent.
  • Guardrails and guidance: Apply version constraints and guardrails using the routing decision-tree to prevent misrouting.

Quick Start

Run the WordPress project triage process to classify the repository and route to the appropriate workflow.

Frequently Asked Questions about wordpress-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I determine if a WordPress codebase is a plugin, theme, or full site?

You can determine the WordPress repo kind by checking repository signals such as composer.json, package.json, block.json, theme.json, and the wp-content directory structure to classify it as a plugin, theme, or full site.

What is WordPress workflow routing and when do I need it?

WordPress workflow routing classifies a codebase and directs tasks to the correct domain workflow, such as plugins or themes. You need it at the start of WordPress tasks to enforce guardrails and prevent misrouting.

How do I route a WordPress task to the correct domain workflow?

Route a WordPress task by running the triage process to classify the repository, then apply the routing decision-tree based on user intent to delegate to the appropriate domain workflow like REST API or WP-CLI.

Can I use a decision-tree to enforce guardrails on a WordPress codebase?

Yes, you can apply a routing decision-tree to enforce guardrails and version constraints on a WordPress codebase, preventing misrouting by ensuring tasks follow the correct domain workflow path.

Does this triage process distinguish between classic themes and block themes?

Yes, the triage process distinguishes between classic themes and block themes by detecting the presence of block.json and theme.json files among the repository signals to classify the codebase accurately.

Why does my WordPress task require classifying the repository before starting?

Classifying the repository before starting prevents misrouting and applies the correct guardrails, ensuring your WordPress task is handled by the appropriate domain workflow rather than a generic process.