Name: plugin-creator
Rating: 68.8 (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

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

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, single-purpose skill with an actionable numbered workflow and clear guardrails. The main gaps are the absence of a copy-paste-ready plugin header example and an explicit verify-failure feedback loop in the workflow.

Suggestions

Add a minimal copy-paste-ready WordPress plugin file header snippet (the `/** Plugin Name: ... */` comment block) so the core artifact is concrete rather than only described.

Turn step 8 ("Activate and verify through `studio`") into an explicit feedback loop: if activation or verification fails, debug and re-verify before calling the `completed` workflow event.

Drop the redundant "Use this skill when the user needs custom WordPress functionality that should survive theme changes" line in the body, since it restates the frontmatter description's trigger clause.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude knows WordPress, and avoids padding, but the opening "Use this skill when the user needs custom WordPress functionality that should survive theme changes" restates the frontmatter description's trigger clause — a minor instance of over-explanation that could be trimmed, placing it at anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	Guidance is mostly executable: concrete paths (`<site-path>/wp-content/plugins/<slug>/`), concrete tool calls (`record_workflow_event` with named params), and specific security practices (capability checks, nonces, sanitize/escape), but it stops short of a copy-paste-ready plugin header snippet, leaving a minor gap versus the anchor 5 example.	4 / 5
Workflow Clarity	The 9-step sequence is clearly ordered and includes a verify step ("Activate and verify through `studio`") plus start/complete workflow events, but it lacks an explicit error-recovery feedback loop (what to do if activation/verification fails), so it sits at anchor 4 rather than the validate→fix→re-validate anchor 5.	4 / 5
Progressive Disclosure	At ~38 lines with no need for external references, the well-organized Ownership / Workflow / Guardrails sections satisfy the rubric's simple-skill exception that progressive disclosure can score 5 with just clear sections and no bundle files.	5 / 5
	Total	17 / 20 Passed

Description

87%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 comprehensive list of capability triggers and a well-scoped niche. The only weakness is that the core action verbs are limited to create/update while the breadth lives mostly in the trigger list.

Dimension	Reasoning	Score
Specificity	"Create or update a custom WordPress plugin" names the action and the long "Use when" clause enumerates several concrete capabilities (admin/settings UI, hooks, REST endpoints, scheduled tasks, integrations, server-side logic), but the action verbs themselves reduce to create/update, leaving minor coverage gaps relative to the comprehensive anchor 5.	4 / 5
Completeness	It explicitly answers both 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...") with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	The "Use when" clause lists natural terms a WordPress user would say — "reusable behavior, admin/settings UI, hooks, REST endpoints, scheduled tasks, integrations, server-side logic" — giving good coverage, though a few common variations (widget, shortcode, cron) are missing, so it sits at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The narrow niche — a custom WordPress plugin that "should not live in a theme or a block" for a "Studio-backed site" — gives it distinct triggers with minimal overlap risk against other skills, matching the anchor 5 clear-niche example.	5 / 5
	Total	18 / 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/claude-code/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.