CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exemplary lean router skill: efficient sections, a concrete executable triage command, a clear numbered workflow with verification and failure-recovery steps, and a textbook progressive-disclosure structure delegating routing detail to a real one-level-deep reference file. The only notable gap is the unspecified provenance of the cross-skill triage script path and the absence of an example triage output.

DimensionReasoningScore

Conciseness

The body is lean and functional throughout — e.g., "Run the triage script: node skills/wp-project-triage/scripts/detect_wp_project.mjs" and the failure-modes list naming exact files ("composer.json, package.json, style.css, block.json, theme.json, wp-content/"). No concept explanations, no padding; every section earns its tokens. The 4 anchor's 'minor instances of over-explanation' does not apply.

5 / 5

Actionability

Quotes: the copy-paste command "node skills/wp-project-triage/scripts/detect_wp_project.mjs", the concrete reference "read: skills/wordpress-router/references/decision-tree.md", and the exact escalation question to ask. Not 5 because the triage script's path provenance (relative to the skills root, not the repo) is not clarified and no example of the triage output structure is shown, even though the decision tree depends on fields like triage.project.kind; not 3 because the guidance is concrete and executable, not pseudocode.

4 / 5

Workflow Clarity

Quotes: numbered procedure (triage → classify → route → guardrails), a Verification section ("Re-run the triage script… Run the repo's lint/test/build commands"), and a failure-recovery loop ("If triage reports kind: unknown, inspect: root composer.json, package.json, style.css…"). Clear sequence with explicit validation and an error-recovery feedback loop; the operation is read-only triage, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

The body is a short, well-sectioned overview that points to one real, one-level-deep bundle file: references/decision-tree.md (verified present, referenced as "For the decision tree, read: skills/wordpress-router/references/decision-tree.md"). Routing detail is appropriately split out and clearly signaled; no inlined content that belongs in a separate file. The 4 anchor's 'minor organization gaps' does not apply.

5 / 5

Total

19

/

20

Passed

Description

83%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.

A strong router description: it explicitly states both what it does (classify repo, route to workflow/skill) and when to use it, with rich natural WordPress vocabulary and enumerated routing targets. The only weaknesses are a thin action verb set and a broad trigger that overlaps with the domain skills it delegates to.

Suggestions

Add a few natural trigger terms users commonly say, such as 'wp-content', 'hooks', or 'functions.php', to broaden keyword coverage toward the top anchor.

Sharpen the trigger to position the skill explicitly as the entry-point/triage step (e.g., 'Use at the start of any WordPress task before picking a domain skill') to reduce overlap risk with the domain skills it routes to.

DimensionReasoningScore

Specificity

Quotes: "quickly classify the repo" and "route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging)" — two concrete actions with comprehensive enumeration of input codebase kinds and routing targets. Not 3 because coverage of the domain is comprehensive rather than partial; not 5 because the action set is only two verbs (classify, route).

4 / 5

Completeness

Quotes: "quickly classify the repo and route to the correct workflow/skill" (what) and "Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts)" (when). Both what and when are explicitly and concretely answered, matching the top anchor; the 4 anchor's 'when could be more specific' does not apply since concrete trigger phrases are listed.

5 / 5

Trigger Term Quality

Quotes: "WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts)", "REST API, WP-CLI", "theme.json" — strong natural keyword coverage including synonyms (block themes / Gutenberg blocks / WP core). Not 5 because a few natural terms users would say are missing (e.g., wp-content, hooks, functions.php, .php files); not 3 because the synonym coverage clearly exceeds 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Quotes: "classify the repo and route to the correct workflow/skill" — a clear router/triage niche with WordPress-specific triggers. Not 5 because the broad trigger "WordPress codebases" fires for nearly every WordPress task, creating inherent overlap with the very domain skills it routes to; not 3 because the routing role is clearly distinguishable from the domain skills themselves.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.