CtrlK
BlogDocsLog inGet started
Tessl Logo

studio

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

64

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/codex/plugins/wordpress-studio/skills/studio/SKILL.md

The canonical home for this skill is studio in Automattic/build-with-wordpress

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 instruction skill with strong workflow sequencing and explicit validation feedback loops. Actionability is high via specific tool names, and progressive disclosure is clean with no unnecessary external references.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and explicitly forbids duplicating generic WordPress guidance; minor redundancy between the Ownership list and the Principle/Workflow sections keeps it just short of fully lean.

4 / 5

Actionability

Concrete tool and command names (site_list, site_info, wp_cli, validate_blocks, take_screenshot, inspect_design, studio site list, ~/Studio, .mcp.json) give clear executable targets, though full copy-paste command syntax is intentionally omitted.

4 / 5

Workflow Clarity

The 13-step workflow has a clear sequence with an explicit mandatory validation loop (validate_blocks, "repeat until the report shows all blocks valid") and screenshot feedback checkpoints, satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

The skill is self-contained with well-organized sections (Ownership, Principle, Workflow, Guardrails), no nested or buried references, and nothing that belongs in a separate file, so structure is easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

65%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 specific and clearly niche-targeted, but it omits an explicit "Use when..." trigger clause, which caps its completeness score. It is concise without being vague, striking a good balance between action naming and token efficiency.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to run or develop a local WordPress site in WordPress Studio."

List one or two more concrete capabilities (e.g., site lifecycle, wp_cli) to lift specificity above 3.

Include a common synonym like "local WP site" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ("local WordPress development") and two concrete mechanisms ("preferring MCP and falling back to the Studio CLI"), but does not enumerate specific actions like site lifecycle, previews, or wp_cli, so it is not comprehensive.

3 / 5

Completeness

The "what" is clear (use Studio, prefer MCP, fall back to CLI), but there is no explicit "Use when..." trigger clause, so per the rubric guidance completeness is capped at 3.

3 / 5

Trigger Term Quality

"WordPress Studio" and "local WordPress development" are exactly the natural terms a user would say; a few minor synonyms (e.g., "local WP site") are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

"WordPress Studio" pins the skill to a specific tool niche with distinct triggers and minimal overlap risk against generic WordPress skills.

5 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Automattic/build-with-wordpress
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.