wordpress

Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening. Includes WordPress 7.0 features: Real-Time Collaboration, AI Connectors, Abilities API, DataViews, and PHP-only blocks.

Quality

56%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/wordpress/SKILL.md

Quality

Content

46%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill attempts to be a comprehensive WordPress development guide but suffers from being a monolithic document that tries to cover too much in a single file. The code examples are a strength—they're concrete, executable, and cover WordPress 7.0 features well—but the overall structure is bloated with feature explanations, obvious use cases, and content that should be split into separate reference files. The workflow phases lack validation checkpoints and concrete verification steps between stages.

Suggestions

Split WordPress 7.0 feature details, code examples (AI Connector, Abilities API, RTC), and directory structures into separate reference files (e.g., WP7-FEATURES.md, PLUGIN-EXAMPLES.md) and reference them from the main skill.

Remove the 'When to Use This Workflow' section and backward compatibility explanations—these are obvious to Claude and waste tokens.

Add explicit validation/verification steps between workflow phases (e.g., 'Verify local environment by running wp --info', 'Run theme-check plugin before proceeding to Phase 3').

Trim the phase action lists to only include non-obvious steps, and convert vague actions like 'Design plugin architecture' into concrete commands or specific guidance.

Dimension	Reasoning	Score
Conciseness	The skill is severely bloated at 440 lines. It extensively explains WordPress 7.0 features (RTC, AI Connectors, Abilities API, DataViews, etc.) that could be in separate reference files. Many sections repeat backward compatibility notes that Claude doesn't need explained. The 'When to Use This Workflow' section states obvious use cases. Multiple code examples are lengthy when shorter snippets would suffice.	2 / 5
Actionability	The skill provides concrete, executable PHP code examples for post type registration, REST API endpoints, AI connector usage, Abilities API, and PHP-only blocks. The code is mostly copy-paste ready with proper sanitization and error handling. However, the workflow phases themselves are more like checklists of vague actions ('Set up local development environment', 'Design theme architecture') rather than specific executable steps, and the 'Copy-Paste Prompts' reference skills that may not exist.	4 / 5
Workflow Clarity	The 8-phase workflow provides a clear sequence, and there are quality gates at the end. However, there are no validation checkpoints between phases, no feedback loops for error recovery, and the individual phase actions are high-level lists without verification steps. For a workflow involving deployment and security hardening (destructive/batch operations), the lack of explicit validation steps caps this at 3.	3 / 5
Progressive Disclosure	This is a monolithic 440-line file with no bundle files provided. The WordPress 7.0 features section, detailed code examples (Abilities API alone is ~60 lines), theme/plugin structures, and WooCommerce examples should clearly be in separate reference files. References to other skills (@app-builder, @frontend-developer, etc.) exist but the actual detailed content is all inlined rather than properly split.	2 / 5
	Total	11 / 20 Passed

Description

66%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.

The description provides good specificity about WordPress development capabilities and includes relevant trigger terms that users would naturally use. Its main weakness is the complete absence of a 'Use when...' clause, which limits Claude's ability to know exactly when to select this skill. The mention of WordPress 7.0 features adds distinctiveness but also raises questions about accuracy since WordPress 7.0 doesn't exist yet.

Suggestions

Add a 'Use when...' clause with explicit trigger phrases like 'Use when the user asks about WordPress themes, plugins, WooCommerce stores, WP performance, or WordPress security'

Include common abbreviations and synonyms like 'WP', 'Gutenberg', 'block editor', 'wp-admin' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Lists several specific actions/domains: theme development, plugin creation, WooCommerce integration, performance optimization, security hardening, plus specific WordPress 7.0 features. However, it reads more like a feature list than concrete actions with verbs.	4 / 5
Completeness	Has a clear 'what' covering WordPress development capabilities, but completely lacks a 'when' clause or explicit trigger guidance. Per rubric guidelines, missing 'Use when...' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains many natural keywords users would say: 'WordPress', 'theme development', 'plugin creation', 'WooCommerce', 'performance optimization', 'security hardening', 'PHP'. Missing some common variations like 'WP', '.php files', 'hooks', 'shortcodes', or 'Gutenberg blocks'.	4 / 5
Distinctiveness Conflict Risk	Fairly distinct due to the specific WordPress ecosystem focus including WooCommerce and WordPress 7.0 features. Minor overlap risk with generic web development or PHP skills, but the WordPress-specific terminology makes it mostly distinguishable.	4 / 5
	Total	15 / 20 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (596 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/wordpress/SKILL.md
Commit: 900c504

Reviewed: 2 hours 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.