Name: wp-env
Rating: 66.4 (1 reviews)
Author: WordPress

wp-env

Use when setting up, configuring, or troubleshooting local WordPress development environments with @wordpress/env (wp-env). Triggers on mentions of wp-env, local WordPress development, Docker-based WordPress, or requests to start/stop/configure a local WordPress instance.

Quality

83%

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

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

A high-quality, execution-ready skill body: every step is a concrete command or config example, inputs are validated up front, verification is an explicit checklist, and a thorough failure-modes table provides recovery guidance. The only weaknesses are mild — slight duplication around Xdebug/PHPUnit and a length that could offload some reference material to separate files.

Dimension	Reasoning	Score
Conciseness	The body is dense with genuinely non-obvious operational detail (default port 8888/8889, credentials, override merge semantics, the bare-slug ZIP-URL gotcha) and assumes Claude's competence — no padding explaining Docker or WordPress basics. Minor instances of tightening possible (Xdebug flags duplicated in section 2 and section 7; PHPUnit mentioned in both "When to use" and section 5), which keeps it below anchor 5.	4 / 5
Actionability	Every section gives copy-paste-ready, executable guidance: install/start commands with flags, a complete .wp-env.json example, source-format table, wp-env run invocations including --env-cwd and -- separator usage, management commands, and a full VS Code launch.json for Xdebug. Common cases are comprehensively covered.	5 / 5
Workflow Clarity	The Procedure is a clearly sequenced 8-step flow preceded by explicit input validation (docker info, node -v), followed by a Verification checklist of five concrete checkpoints, and a symptom→cause→fix failure-modes table that provides error-recovery feedback loops. This matches the anchor for explicit validation steps with feedback loops and checklists.	5 / 5
Progressive Disclosure	No bundle files exist, so the skill is self-contained; sections are well-organized and the References section points to clearly signaled, one-level-deep external docs. At ~215 lines, some inline material (the full .wp-env.json field reference, the failure-modes table, Xdebug IDE setup) could arguably live in separate reference files, which is the minor-organization-gap case of anchor 4 rather than 5.	4 / 5
	Total	18 / 20 Passed

Description

70%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 trigger-focused description with explicit and concrete "Use when"/"Triggers on" clauses and good natural keyword coverage. Its main weakness is that the skill's capabilities are only implied through trigger phrasing — the verbs (set up, configure, troubleshoot) are generic and never state what the skill concretely does.

Suggestions

Add a leading capability statement naming concrete actions, e.g., "Sets up and manages Docker-based local WordPress environments with @wordpress/env: start/stop environments, run WP-CLI and PHPUnit, configure .wp-env.json, and debug with Xdebug."

Include ".wp-env.json" as a trigger term, since users asking about that config file would benefit from this skill.

Sharpen the trigger list to distinguish wp-env from sibling local-WordPress options (e.g., "Docker-based" or ".wp-env.json" presence) to reduce overlap risk with a wp-playground-style skill.

Dimension	Reasoning	Score
Specificity	"Setting up, configuring, or troubleshooting" names three actions, but all are generic verbs with no concrete capabilities (e.g., running WP-CLI commands, PHPUnit tests, or Xdebug debugging that the skill actually covers). The domain is specific, but the action list is not comprehensive enough for anchor 4.	3 / 5
Completeness	The "when" is fully explicit via both "Use when setting up, configuring, or troubleshooting..." and "Triggers on mentions of...", but the "what" is only implicit inside the trigger phrasing — there is no standalone capability statement. Not anchor 5, which requires both to be clearly and explicitly stated.	4 / 5
Trigger Term Quality	Triggers on "wp-env", "@wordpress/env", "local WordPress development", "Docker-based WordPress", and "start/stop/configure a local WordPress instance" — good natural keyword coverage. A few natural terms are missing (e.g., ".wp-env.json", "local WordPress site"), keeping it below anchor 5's comprehensive synonym/extension coverage.	4 / 5
Distinctiveness Conflict Risk	"wp-env", "@wordpress/env", and "Docker-based WordPress" carve a distinct niche with minimal conflict risk against unrelated skills. However, "local WordPress development" would also naturally trigger a sibling WordPress-local-dev skill (e.g., wp-playground), which is exactly the minor-overlap-with-closely-related-skills case of anchor 4.	4 / 5
	Total	15 / 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/wp-env/SKILL.md
Commit: 3cf7f6f

Reviewed: 8 days 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.