Name: wordpress-plugin-development
Rating: 54.400000000000006 (1 reviews)
Author: administrakt0r

wordpress-plugin-development

WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, security best practices, and WordPress 7.0 features: Real-Time Collaboration, AI Connectors, Abilities API, DataViews, and PHP-only blocks.

Quality

61%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wordpress-plugin-development/SKILL.md

The canonical home for this skill is wordpress-plugin-development in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

57%Weight 40%Scale 1-5

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

The content is a thorough, actionable WordPress plugin workflow with strong code examples, but it is held back by missing validation feedback loops in destructive phases and a monolithic single-file structure with no progressive disclosure. Splitting 7.0 feature details into reference files and adding explicit validate/retry checkpoints would lift the weaker dimensions.

Suggestions

Add explicit validation checkpoints inside destructive/batch phases (e.g. after database schema creation: run a migration check before proceeding; verify nonce + capability before any save_post AI action).

Move the large 7.0 feature code (AI Connector, Abilities API, PHP-only blocks) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Trim redundant token spend: drop the Overview restatement of the description and collapse the repeated per-phase "Copy-Paste Prompts" blocks into a single prompt catalog.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete code, but the Overview restates the description and repeated "Copy-Paste Prompts" plus per-phase "Skills to Invoke" blocks add tokens without proportional value.	3 / 5
Actionability	Provides concrete, largely copy-paste-ready code (register_post_meta with show_in_rest, wp_ai_client_prompt, Abilities API registration, PHP-only block render_callback) covering common cases, with only minor gaps like the undefined handleViewChange reference.	4 / 5
Workflow Clarity	Nine phases are clearly sequenced with end-of-workflow checklists, but phases involving destructive/batch operations (database, security) lack explicit validate-then-proceed feedback loops, capping this at 3 per the rubric.	3 / 5
Progressive Disclosure	Sections are well-organized, but no bundle files exist and all content (including sizable 7.0 feature code that could live in references) is inlined in SKILL.md with no one-level-deep file references.	3 / 5
	Total	13 / 20 Passed

Description

66%Weight 40%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 is specific and well-targeted to WordPress plugin development including 7.0 features, but it omits any explicit "Use when..." trigger guidance, which limits its completeness score. Adding a usage-trigger clause would raise it into the top band.

Suggestions

Append an explicit trigger clause, e.g. "Use when creating or extending WordPress plugins, especially when integrating WordPress 7.0 AI, collaboration, or block features."

Include common synonyms/file cues a user might say, such as ".php plugins", "WP plugin", or "Gutenberg blocks".

Reframe topic areas as discrete actions (e.g. "scaffold, register hooks, build admin screens, expose REST endpoints") to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete domains ("plugin architecture, hooks, admin interfaces, REST API, security best practices") plus named 7.0 features, giving broad coverage, though framed as topic areas rather than discrete actions.	4 / 5
Completeness	Clearly states what the skill covers, but there is no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ("WordPress plugin development", "hooks", "REST API", "admin interfaces") with good coverage, but lacks synonyms or file extensions like ".php".	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (WordPress plugin development with specific 7.0 features) making it mostly distinct from sibling skills, with only minor overlap risk against general WordPress or theme/woocommerce workflows.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wordpress-plugin-development/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.