studio

Use WordPress Studio for local WordPress development, preferring MCP and falling back to the Studio CLI when needed.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/studio/SKILL.md

Quality

Content

81%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 content is a well-structured, lean workflow with strong validation feedback loops and concrete tool guidance, scoring at the top of the range for workflow clarity. Its only notable gaps are minor redundancy between sections and the lack of external reference files for the lengthy block-repair procedure.

Suggestions

De-duplicate the 'prefer MCP over shell' guidance that appears in both the Principle and Guardrails sections to tighten conciseness toward a 5.

Extract the detailed validate_blocks repair sub-procedure (step 10) into a reference file and link to it one level deep, which would both shorten the body and raise progressive disclosure.

Add one or two copy-paste-ready example invocations (e.g. a `studio wp` or `validate_blocks` call with arguments) to push actionability toward fully executable.

Dimension	Reasoning	Score
Conciseness	The body is lean and direct with no padded conceptual explanation, but the Principle and Guardrails sections restate the 'prefer MCP over shell' guidance, leaving minor instances that could be trimmed rather than the tight 'every token earns its place' of a 5.	4 / 5
Actionability	It names concrete commands and exact MCP tools with specific decision rules, but it does not provide full copy-paste code blocks, placing it at 'mostly executable; concrete commands with minor gaps' rather than the fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	The 13-step sequence has explicit validation checkpoints and feedback loops ('repeat until the report shows all blocks valid', rewrite HTML blocks then re-validate), matching 'clear sequence with explicit validation steps and feedback loops for error recovery'.	5 / 5
Progressive Disclosure	The body is self-contained with clear sections and no broken or nested references, but at ~83 lines it exceeds the under-50-line simple-skill exception and could split the detailed validate_blocks repair loop into a reference file, leaving it at 'good structure; minor organization gaps'.	4 / 5
	Total	17 / 20 Passed

Description

61%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 concise and names a clear niche with solid natural trigger terms, but it omits an explicit 'Use when...' activation clause, which caps its completeness. Adding concrete trigger phrases would lift it from good to comprehensive.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when the user wants to run, preview, or develop a local WordPress site in WordPress Studio'.

List one or two more concrete actions (e.g. site lifecycle, previews, block validation) to raise specificity from 3 toward 4-5.

Include common synonyms or aliases users say (e.g. 'WP', 'local site') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain (local WordPress development) and two concrete mechanisms (MCP and Studio CLI fallback) but lists fewer discrete actions than the anchor-4 example, fitting 'names domain and 1-2 concrete actions' better than the multi-action anchor above.	3 / 5
Completeness	It has a clear 'what' but no explicit 'Use when...' trigger clause, and the rubric caps completeness at 3 when that guidance is missing.	3 / 5
Trigger Term Quality	Natural terms users would say are present ('WordPress Studio', 'local WordPress development', 'WordPress'), but common synonyms like 'WP' or 'local site' are missing, matching 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	'WordPress Studio' is a specific niche with low conflict risk against non-WordPress skills, though there is minor overlap with generic WordPress skills, matching 'mostly distinct; minor overlap risk'.	4 / 5
	Total	14 / 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: Automattic/build-with-wordpress
Path: skills/studio/SKILL.md
Commit: b4fc8b7

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