Name: plugin-creator
Rating: 67.2 (1 reviews)
Author: Automattic

plugin-creator

Create or update a custom WordPress plugin for site functionality that should not live in a theme or a block. Use when the user needs reusable behavior, admin/settings UI, hooks, REST endpoints, scheduled tasks, integrations, or server-side logic for a Studio-backed site.

Quality

81%

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

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

Quality

Content

78%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 concise, well-structured instruction skill with a clear numbered workflow, concrete paths and tool calls, and explicit security guardrails. The main gap is an implicit rather than explicit validation/feedback loop in the workflow.

Suggestions

Make the verify step explicit and add a short feedback loop, e.g. "If activation or verification fails through `studio`, review the error, fix, and re-verify before marking the workflow completed" to lift workflow_clarity toward 5.

Trim or sharpen the fluffy guardrail ("Keep the plugin editable and easy to reason about") into a concrete directive so conciseness reaches 5.

Add one minimal copy-paste-ready plugin header snippet to move actionability from mostly-executable to fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's knowledge of WordPress, with no padded concept explanations; the slightly fluffy guardrail "Keep the plugin editable and easy to reason about" keeps it at 4 (efficient, minor trimmable instances) rather than 5.	4 / 5
Actionability	Concrete guidance is present throughout ("Create the plugin under `<site-path>/wp-content/plugins/<slug>/`", "call `record_workflow_event` with `workflow: \"plugin-build\" and `stage: \"started\"`", "enforce capability checks and nonces, sanitize on input, and escape on output"), giving mostly executable direction with minor gaps and no full copy-paste code example, matching the 4 anchor.	4 / 5
Workflow Clarity	A clear nine-step numbered sequence with a verify step (step 8: "Activate and verify through `studio`") and started/completed event checkpoints; it stays at 4 rather than 5 because the validation is somewhat implicit with no explicit error-recovery feedback loop.	4 / 5
Progressive Disclosure	The body is under 50 lines with no need for external references and is organized into clear sections (Ownership, Workflow, Guardrails), which per the simple-skill scoring note earns the top score on progressive disclosure.	5 / 5
	Total	17 / 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, third-person description that clearly states both what the skill does and when to use it, with a concrete capability list and an explicit niche boundary against theme/block skills. Trigger-term coverage is good but could add a few synonyms to reach the top anchor.

Suggestions

Add a couple of natural synonyms or common phrasings users might say (e.g. "custom plugin", "extend WordPress", ".php plugin file") to lift trigger_term_quality from 4 to 5.

Consider one more concrete action verb (e.g. "register shortcodes" or "add settings pages") to close the minor specificity gap toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Create or update a custom WordPress plugin" names the domain and concrete actions, and the trigger list (admin/settings UI, hooks, REST endpoints, scheduled tasks, integrations, server-side logic) covers several specific capabilities with only minor gaps, matching the anchor for several specific actions rather than the comprehensive 5.	4 / 5
Completeness	It explicitly states what ("Create or update a custom WordPress plugin for site functionality that should not live in a theme or a block") and when ("Use when the user needs reusable behavior, admin/settings UI, hooks, REST endpoints, scheduled tasks, integrations, or server-side logic") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	"Use when the user needs reusable behavior, admin/settings UI, hooks, REST endpoints, scheduled tasks, integrations, or server-side logic" plus "WordPress plugin" gives good natural-term coverage; it falls short of 5 because it lacks synonyms/file extensions and a couple of common phrasings users might say.	4 / 5
Distinctiveness Conflict Risk	"should not live in a theme or a block" and "Studio-backed site" carve a clear niche with distinct triggers, but there is minor overlap risk with closely related general WordPress skills, so it sits at 4 rather than 5.	4 / 5
	Total	17 / 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: plugins/codex/plugins/wordpress-studio/skills/plugin-creator/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.