wordpress-pro
tessl i github:jeffallan/claude-skills --skill wordpress-proUse when developing WordPress themes, plugins, customizing Gutenberg blocks, implementing WooCommerce features, or optimizing WordPress performance and security.
Validation
75%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
Implementation
42%This skill has strong structural organization with excellent progressive disclosure through its reference table system. However, it critically lacks actionable code examples - the entire document describes what to do without showing how. The constraints lists are valuable but would benefit from concrete code snippets demonstrating proper sanitization, escaping, and nonce usage.
Suggestions
Add executable code examples for critical patterns: nonce implementation, input sanitization (sanitize_text_field, wp_kses), output escaping (esc_html, esc_attr), and prepared statements ($wpdb->prepare)
Include a minimal working example of a plugin header or theme functions.php snippet that demonstrates proper hook usage
Add validation checkpoints to the Core Workflow, such as 'Run PHPCS check' after implementation and 'Security scan' before deployment
Condense the Role Definition and When to Use sections into the description or remove them entirely - Claude can infer this context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'Role Definition' and 'When to Use This Skill' that explain context Claude can infer. The MUST DO/MUST NOT DO lists are comprehensive but could be more condensed. However, it avoids explaining basic WordPress concepts. | 2 / 3 |
Actionability | The skill lacks any executable code examples. It describes what to do ('Use nonces', 'Sanitize inputs') but provides no concrete implementations, function calls, or copy-paste ready snippets. The guidance is entirely abstract and descriptive. | 1 / 3 |
Workflow Clarity | The 5-step 'Core Workflow' provides a sequence but lacks validation checkpoints or feedback loops. For WordPress development involving security-sensitive operations, there's no explicit validation step between implementation and deployment. | 2 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear topics, file paths, and 'Load When' guidance. References are one level deep and well-signaled. The main skill serves as a proper overview pointing to detailed materials. | 3 / 3 |
Total | 8 / 12 Passed |
Activation
55%This description has strong trigger term coverage and clear distinctiveness within the WordPress ecosystem, but critically fails on completeness by only specifying when to use the skill without explaining what it actually does. The lack of concrete actions (only domain categories are listed) further weakens its utility for skill selection.
Suggestions
Add a 'what' clause before the 'Use when' that describes concrete capabilities, e.g., 'Creates custom themes and plugins, builds Gutenberg blocks, configures WooCommerce stores, and implements security hardening.'
Replace category mentions with specific actions: instead of 'developing WordPress themes', use 'create child themes, customize template hierarchies, implement theme options panels'
Restructure to follow the pattern: '[What it does]. Use when [triggers].' to ensure both components are clearly present.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (WordPress) and mentions several areas (themes, plugins, Gutenberg blocks, WooCommerce, performance, security), but these are categories rather than concrete actions. No specific verbs describing what actions are performed (e.g., 'create custom post types', 'configure caching'). | 2 / 3 |
Completeness | The description only provides 'when' guidance but completely lacks the 'what' component. There's no explanation of what capabilities or actions this skill provides - it jumps straight to trigger conditions without establishing what the skill actually does. | 1 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'WordPress', 'themes', 'plugins', 'Gutenberg blocks', 'WooCommerce', 'performance', 'security'. These are all terms developers naturally use when seeking WordPress help. | 3 / 3 |
Distinctiveness Conflict Risk | WordPress ecosystem is a clear niche with distinct terminology (Gutenberg, WooCommerce, themes, plugins). Unlikely to conflict with general web development or other CMS skills due to WordPress-specific terms. | 3 / 3 |
Total | 9 / 12 Passed |
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.