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.
71
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (WordPress plugin creation/updates), explicitly distinguishes itself from related skills (themes, blocks), and provides a comprehensive 'Use when' clause with specific trigger terms. The description is concise yet thorough, covering both the what and when effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create or update a custom WordPress plugin', 'reusable behavior, admin/settings UI, hooks, REST endpoints, scheduled tasks, integrations, server-side logic'. These are concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create or update a custom WordPress plugin for site functionality not in a theme or block) and 'when' (explicit 'Use when' clause listing specific trigger scenarios like hooks, REST endpoints, scheduled tasks, etc.). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'WordPress plugin', 'hooks', 'REST endpoints', 'scheduled tasks', 'integrations', 'admin/settings UI', 'server-side logic', 'Studio-backed site'. These cover a wide range of natural user language for this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to WordPress plugins specifically, with explicit exclusion of theme and block functionality. The mention of 'Studio-backed site' and specific plugin concerns (hooks, REST endpoints, scheduled tasks) creates a distinct niche unlikely to conflict with theme or block skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that clearly delineates ownership boundaries and provides a sensible workflow. Its main weakness is the lack of concrete, executable examples—a plugin header template, a sample hook registration pattern, or a nonce/capability check snippet would significantly improve actionability. The workflow would also benefit from an explicit validation checkpoint before activation.
Suggestions
Add a concrete plugin header template (the standard WordPress plugin file header comment block) as a code example in the workflow.
Include a brief executable example of a capability check + nonce pattern, since security enforcement is called out as a requirement but no reference implementation is provided.
Add an explicit validation step between file creation and activation (e.g., 'Run `wp plugin list` to confirm the plugin appears, then activate').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what plugins are, what WordPress is, or how hooks work. Every line provides actionable guidance or a meaningful constraint. No wasted tokens. | 3 / 3 |
Actionability | The workflow provides clear steps and mentions specific paths (`<site-path>/wp-content/plugins/<slug>/`), but lacks concrete code examples—no plugin header template, no example hook registration, no sample nonce/capability check. These are the kind of specifics that would make the skill copy-paste ready. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced and include activation/verification at the end, but there's no explicit validation checkpoint between creation and activation. For a file-creation workflow, there should be a verify/test step (e.g., check for PHP syntax errors, confirm the plugin appears in the list) before activation, and no error recovery loop is described. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~40 lines) with no bundle files, the content is well-organized into clear sections (Ownership, Workflow, Guardrails) with appropriate delegation to the `studio` skill. No external references are needed and none are fabricated. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Automattic/build-with-wordpress
- Commit
1c076c2
- 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.