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.
68
82%
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 an excellent skill description that thoroughly covers the WordPress development domain with specific, concrete actions and comprehensive trigger terms. It follows the recommended pattern with a clear 'what it does' section followed by an explicit 'Use when...' clause. The description uses proper third-person voice and includes both high-level capabilities and specific technical details (nonces, sanitization, escaping) that serve as effective trigger terms.
| 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' (develops themes, plugins, Gutenberg blocks, WooCommerce configuration, REST API endpoints, security hardening, performance optimization) AND 'when should Claude use it' with an explicit 'Use when...' clause listing multiple trigger scenarios. | 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 WordPress-specific terminology throughout. The combination of WordPress, Gutenberg, WooCommerce, ACF, hooks and filters, and WordPress REST API creates a clear niche that is unlikely to conflict with general web development or other CMS skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid WordPress skill with excellent actionability — the code examples are complete, executable, and cover the most critical security patterns. The progressive disclosure structure is well-designed in concept but unsupported by actual bundle files, and the workflow could benefit from explicit feedback loops for validation failures. Some conciseness gains are possible by trimming redundant constraint listings and the keyword dump at the end.
Suggestions
Add explicit feedback loops to the Core Workflow, e.g., 'If phpcs reports violations, fix and re-run until clean' and 'If nonce/capability audit finds gaps, address before proceeding'.
Provide the referenced bundle files (references/theme-development.md, etc.) or remove the reference table to avoid pointing to non-existent resources.
Remove redundant items from MUST DO/MUST NOT DO lists that are already demonstrated in the code examples, and drop the 'Knowledge Reference' keyword line.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good code examples, but the Constraints section has some redundancy with patterns already shown (e.g., nonce verification is both demonstrated and listed as a MUST DO). The 'Knowledge Reference' line at the end is a keyword dump that adds little value. Some items in MUST NOT DO are obvious to Claude (e.g., 'Trust user input without sanitization'). | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready PHP code for all key patterns: nonce verification, sanitization/escaping, script enqueuing, prepared queries, and capability checks. Each example is complete and follows WordPress coding standards with proper function signatures and context. | 3 / 3 |
Workflow Clarity | The Core Workflow provides a clear 6-step sequence with a validation step (phpcs), but lacks explicit feedback loops — there's no 'if phpcs fails, fix and re-run' instruction. For a skill involving security-critical operations (sanitization, nonce handling, database queries), the validation/verification steps could be more explicit with error recovery paths. | 2 / 3 |
Progressive Disclosure | The reference table with 5 topic-specific files is well-structured and clearly signaled with 'Load When' guidance. However, no bundle files were provided, meaning all referenced files (references/theme-development.md, etc.) are missing. The main SKILL.md also includes substantial inline content (key patterns, constraints, output templates) that could arguably be split into references, making the file somewhat long. | 2 / 3 |
Total | 9 / 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
e8be415
- 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.