CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

studio

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

Quality

74%

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/cursor/skills/studio/SKILL.md

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

SKILL.md
Quality
Evals
Security

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.

A well-structured, largely lean instruction skill: the workflow has explicit verification checkpoints and a genuine validate-and-repair feedback loop, and guardrails are concrete rather than abstract. Remaining gaps are minor redundancy in the tool-preference rule and the absence of example tool invocations.

Suggestions

State the MCP-over-shell preference once (in Principle) and reference it from Workflow/Guardrails instead of restating it, trimming the Ownership list to the dedup pointer only.

Add one or two concrete example invocations, e.g. a sample `wp_cli` call and the fallback `studio wp` command form, so the CLI-fallback path is copy-paste executable.

Consider moving the detailed validate_blocks repair-loop rules (step 10 sub-bullets) into a short reference file to keep SKILL.md under the ~50-line ideal while preserving the mandatory-loop summary inline.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanations of concepts Claude already knows, and it explicitly says 'Keep this skill minimal. Do not duplicate command syntax or generic WordPress guidance'. It falls short of 5 because the MCP-over-shell preference is stated three times (Principle, Workflow, Guardrails) and the meta 'Ownership' list adds bulk that could be trimmed.

4 / 5

Actionability

Concrete, executable guidance throughout: 'run `studio site list`', MCP tool names ('site_list', 'site_info', 'validate_blocks', 'take_screenshot', 'inspect_design'), the 'filePath' argument, and a numbered 13-step procedure. It is not a 5 because no example invocations are given for `wp_cli` or the fallback 'smallest `studio` CLI command' — the reader must construct those calls themselves.

4 / 5

Workflow Clarity

The workflow is a clear 13-step sequence with environment verification first, explicit MCP-confirmation steps, and a mandatory validate-fix-repeat feedback loop: 'run `validate_blocks`... treat every `validate_blocks` issue as a required fix step... repeat until the report shows all blocks valid'. This matches the anchor with explicit validation steps and error-recovery loops, including auto-fix diff handling.

5 / 5

Progressive Disclosure

No bundle files exist, and the content is well organized into clearly signaled sections (Ownership, Principle, Workflow, Guardrails) with nothing buried. It does not reach 5 because the body is ~82 lines — above the under-50-line simple-skill guideline — with all content inline, so a small split (e.g. the validate_blocks repair-loop detail) would earn the top anchor.

4 / 5

Total

17

/

20

Passed

Description

53%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 clearly identifies its niche and tool-preference behavior, but reads as a one-sentence summary rather than a complete trigger description: it lacks an explicit 'Use when' clause, lists few concrete actions, and omits natural keyword variations. It is serviceable but well below the good-example standard.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to run, build, or test a WordPress site locally in WordPress Studio, or mentions WordPress Studio, local WordPress development, or local WP sites.'

List 2-3 concrete capabilities in the description (e.g. site lifecycle, wp_cli operations, block validation, screenshots) so the 'what' is specific rather than only naming the tool preference.

Include natural synonyms and variations users would say ('run WordPress locally', 'local WP environment', 'wp-cli') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('WordPress Studio', 'local WordPress development') and the tool-preference actions ('preferring MCP and falling back to the Studio CLI'), but lists no concrete capability actions such as creating sites, running wp-cli, or validating blocks. It matches the 'names domain and 1-2 concrete actions' anchor rather than the 'lists several specific actions' anchor above.

3 / 5

Completeness

It has a clear 'what' (use WordPress Studio for local development, preferring MCP with CLI fallback) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The 'when' is only weakly implied by 'local WordPress development'.

3 / 5

Trigger Term Quality

'WordPress Studio', 'local WordPress development', 'MCP', and 'Studio CLI' are relevant keywords, but common natural variations users would say ('run WordPress locally', 'local WP site', 'local development environment') are missing. Coverage is more than one or two generic keywords (ruling out 2) but not yet 'good coverage missing only a few' (4).

3 / 5

Distinctiveness Conflict Risk

'WordPress Studio' plus the MCP/CLI framing carves out a clear niche with mostly distinct triggers, but the generic 'WordPress development' wording leaves minor overlap risk with broader WordPress or local-dev skills, keeping it below the 'clear niche, minimal conflict risk' anchor 5.

4 / 5

Total

13

/

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

Automattic/build-with-wordpress

Path

plugins/cursor/skills/studio/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.