CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wordpress-plugin-development

Use when creating WordPress plugins: hooks, admin interfaces, custom tables, REST endpoints, Abilities API, AI Client integration, PHP-only blocks, security hardening, or plugin test setup. Do not use for theme templates or storefront setup; use wordpress-theme-development or wordpress-woocommerce-development.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 body delivers genuinely valuable, current version-specific guidance with strong executable examples, but it is a monolithic 580-line file padded with generic action checklists and a redundant when-to-use section. Database upgrade work lacks validation checkpoints, and reference-grade material should be split into bundle files.

Suggestions

Cut the generic per-phase "Actions" lists (e.g., "Register action hooks / Create filter hooks / Implement callback functions") and the "When to Use This Workflow" section, which duplicates the frontmatter description — keep only the version-specific considerations under each phase.

Add explicit validation checkpoints to Phase 5's database work: verify upgrade routines against a test copy (fix-and-re-run loop) before applying schema changes, mirroring the Plugin Check gate already present.

Split reference-grade material into bundle files (e.g., references/phpcs-compliance.md for the Plugin Check annotation patterns and references/wp-7x-features.md for the 7.0/7.1 changelog), keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

DimensionReasoningScore

Conciseness

The version-specific material (7.0/7.1 gotchas, phpcs annotations, code examples) earns its place, but the "When to Use This Workflow" section duplicates the frontmatter and the nine "Actions" lists state knowledge Claude already has ("1. Register action hooks / 2. Create filter hooks / 3. Implement callback functions"). Mostly efficient with unnecessary sections that could be trimmed, per the anchor-3 example, rather than the minor-trim of anchor 4.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready guidance: `$wpdb->prepare( 'SELECT * FROM %i WHERE id = %d', ...)` with exact phpcs annotations, a full `wp_ai_client_prompt(...)->using_temperature(0.3)->generate_text()` example, and the `wp plugin check <plugin-slug>` command. Not 5 because a few examples are fragmentary — the phpcs:disable SQL elides `INNER JOIN ( ... WHERE product_id IN ...)` and the PHP-only block section says "create a block.json file" without ever showing it.

4 / 5

Workflow Clarity

Nine phases are clearly sequenced (Setup → Architecture → Hooks → Admin → Database → REST → Security → Features → Testing) with end-of-workflow gates ("All code must pass with 0 errors and 0 warnings", Quality Gates checklist). However Phase 5 includes destructive database work ("Create data upgrade routines") with no validation or fix-and-retry loop, and the rubric caps workflows involving destructive/batch operations without validation at 3.

3 / 5

Progressive Disclosure

No bundle files exist, so all ~580 lines live in SKILL.md, including reference-style material (the Plugin Check/phpcs compliance guide, the 7.0/7.1 feature changelog) that clearly belongs in separate files. Good section headers keep it navigable, matching anchor 3's "some structure but content that should be separate is inline" rather than anchor 2's minimal structure.

3 / 5

Total

13

/

20

Passed

Description

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

An exemplary description: explicit use-when triggers, a comprehensive concrete capability list, and proactive disambiguation against sibling WordPress skills. Both what and when are answered clearly with no padding.

DimensionReasoningScore

Specificity

Lists nine concrete capabilities ("hooks, admin interfaces, custom tables, REST endpoints, Abilities API, AI Client integration, PHP-only blocks, security hardening, or plugin test setup"), matching the comprehensive multi-action anchor. Not 4 because no meaningful capability area of WordPress plugin development is left uncovered.

5 / 5

Completeness

Opens with an explicit "Use when creating WordPress plugins" trigger clause and enumerates exactly what the skill covers, plus explicit negative scope ("Do not use for theme templates or storefront setup"). Not 4 because both what and when are fully explicit with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers both everyday phrases users would naturally say ("creating WordPress plugins", "REST endpoints", "plugin test setup") and niche feature triggers ("Abilities API", "PHP-only blocks", "AI Client integration"). Not 4 because the natural-term coverage spans generic through specialized with no obvious gaps.

5 / 5

Distinctiveness Conflict Risk

Actively disambiguates sibling skills ("use wordpress-theme-development or wordpress-woocommerce-development") and carves out a clear plugin-development niche. Not 4 because it not only avoids overlap but names where overlapping requests should go.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (583 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

administrakt0r/pro-skills-repo-administraktor

Path

skills/wordpress-skills/wordpress-plugin-development/SKILL.md

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.