Name: wordpress-router
Rating: 71.2 (1 reviews)
Author: WordPress

wordpress-router

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

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured router skill: a concrete executable triage command, a real one-level-deep reference for the decision tree, and clear verification and failure-recovery sections. It assumes Claude's competence and avoids concept padding. The main weakness is conditional rather than mandatory verification.

Suggestions

Make verification less conditional by stating a concrete default (e.g., 'run `npm test` / `composer test` if the triage output lists them') rather than 'if available'.

Add an explicit validate-then-proceed checkpoint in the Procedure (e.g., 'Only route after triage reports a non-unknown kind') to tighten the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no explanation of what WordPress is or how triage works — with only minor redundancy between the 'When to use' enumeration and the Procedure section, keeping it just below the fully lean anchor.	4 / 5
Actionability	Provides a fully executable command ('node skills/wp-project-triage/scripts/detect_wp_project.mjs'), a concrete reference path, and a precise list of files to inspect on failure (composer.json, package.json, style.css, block.json, theme.json, wp-content/), covering the common cases copy-paste ready.	5 / 5
Workflow Clarity	A clear numbered Procedure (triage → classify → route → guardrails) with an explicit Verification step (re-run triage after restructuring, run recommended lint/test/build) and a Failure modes recovery branch, but verification is partly conditional ('if available') and lacks an explicit validate-then-proceed checkpoint.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview that points to one well-signaled one-level-deep reference ('read: skills/wordpress-router/references/decision-tree.md', which exists) and the triage script, with the body cleanly sectioned into When to use, Inputs, Procedure, Verification, Failure modes, and Escalation.	5 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-constructed: it pairs an explicit 'Use when...' trigger with concrete classification/routing actions and a comprehensive enumeration of WordPress repo types. It uses clean third-person voice and avoids fluff. The only gap is a lack of file-extension triggers and slightly limited action verb diversity.

Suggestions

Add natural file-extension or filename triggers (e.g., '.php', 'functions.php', 'style.css', 'block.json') to round out trigger-term coverage.

Consider framing the 'what' as a few more distinct verbs (e.g., 'classify, route, and apply guardrails') to lift specificity from several actions toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names the WordPress domain plus two concrete actions ('classify the repo' and 'route to the correct workflow/skill') with extensive sub-type coverage (plugins, themes, block themes, Gutenberg blocks, WP core checkouts), but the action verbs are essentially two rather than a list of several, so it sits just below the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what ('classify the repo and route to the correct workflow/skill' with enumerated routing targets) and when ('Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts)') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural terms users would say ('WordPress codebases', 'plugins', 'themes', 'block themes', 'Gutenberg blocks', 'WP core checkouts') with an explicit 'Use when the user asks about...' trigger, but it omits file extensions and specific filenames (.php, functions.php, style.css, block.json) that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	A clearly bounded WordPress-only routing niche with distinct triggers (WordPress codebases, Gutenberg blocks, WP core checkouts) and minimal conflict risk, since its job is to classify and delegate rather than perform the domain work itself.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: WordPress/agent-skills
Path: skills/wordpress-router/SKILL.md
Commit: d87ee69

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.