wordpress-pro
Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.
93
86%
Does it follow best practices?
Impact
97%
1.12xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
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 an excellent skill description that thoroughly covers WordPress development capabilities with specific, concrete actions and technologies. It includes a comprehensive 'Use when...' clause with natural trigger terms that WordPress developers would actually use. The description is well-structured, uses third person voice correctly, and is clearly distinguishable from other potential skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: developing themes/plugins, creating Gutenberg blocks and block patterns, configuring WooCommerce, implementing REST API endpoints, applying security hardening (with specific techniques like nonces, sanitization, escaping, capability checks), and optimizing performance through caching and query tuning. | 3 / 3 |
Completeness | Clearly answers both 'what does this do' (first half lists specific capabilities) AND 'when should Claude use it' with an explicit 'Use when...' clause covering multiple trigger scenarios like building themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, etc. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: WordPress themes, plugins, Gutenberg blocks, WooCommerce, ACF, WordPress REST API, hooks and filters, nonces, sanitization, escaping, performance, security. These are all terms a developer would naturally use when seeking WordPress help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in WordPress development. The specific mentions of WordPress-specific concepts (Gutenberg, WooCommerce, ACF, hooks and filters, nonces) make it very unlikely to conflict with general web development or other CMS 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 WordPress skill with strong actionability through executable code examples and excellent progressive disclosure via a clear reference table. The main weaknesses are some verbosity in the constraints sections (listing things Claude already knows about security) and a workflow that lacks explicit feedback loops for validation failures. The Output Templates and Knowledge Reference sections add little actionable value.
Suggestions
Add an explicit feedback loop to the Core Workflow validation step (e.g., 'If phpcs reports violations: fix → re-run → only proceed when clean')
Trim the MUST DO/MUST NOT DO lists to only WordPress-specific constraints Claude wouldn't already know, removing generic security advice like 'don't trust user input'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but the MUST DO/MUST NOT DO lists are somewhat verbose and include items Claude would already know (e.g., 'don't trust user input without sanitization'). The Knowledge Reference section at the bottom is just a keyword list that adds little value. The Output Templates section is vague filler. | 2 / 3 |
Actionability | The code examples are fully executable, copy-paste ready PHP covering nonce verification, sanitization/escaping, enqueuing, prepared queries, and capability checks. Each pattern is concrete with proper WordPress function calls and realistic usage contexts. | 3 / 3 |
Workflow Clarity | The core workflow has 6 numbered steps with a validation step (phpcs), but the validation is only mentioned briefly without a feedback loop for fixing issues. For a skill involving security-critical operations like database queries and file handling, the workflow lacks explicit checkpoints for error recovery and re-validation after fixes. | 2 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear 'Load When' guidance pointing to five separate reference files. The main skill provides a concise overview with key patterns inline while deferring detailed topic-specific guidance to one-level-deep references. | 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
- jeffallan/claude-skills
- Commit
3d95bb1
- 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.