CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

68%

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

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

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.

A well-sequenced, code-rich workflow whose main costs are generic action-list padding and the absence of in-phase validation loops (notably around destructive database/upgrade operations). Everything lives inline in one long file with no reference files, which limits progressive disclosure.

Suggestions

Replace the generic per-phase 'Actions' lists (e.g., 'Implement singleton pattern', 'Register action hooks') with either concrete commands/code or a pointer, cutting roughly a third of the body's tokens.

Add explicit validation checkpoints to destructive/batch phases — e.g., after Phase 5 database writes and upgrade routines, verify row counts/schema version before proceeding, mirroring the 'validate -> fix -> retry' pattern the rubric expects.

Move the long WP 7.0 code examples (AI Connector, Abilities API, PHP-only block) into one-level-deep reference files (e.g., references/wp7-features.md) and keep short inline pointers plus the compatibility checklist in SKILL.md; also define or stub `handleViewChange` in the DataViews example so it runs as written.

DimensionReasoningScore

Conciseness

The body is mostly efficient — the PHP/JS code blocks earn their tokens — but each phase's generic 'Actions' lists restate knowledge Claude already has (e.g., 'Implement singleton pattern', 'Create loader class', 'Register action hooks', 'Sanitize all inputs'), and the repeated 'Skills to Invoke' / 'Copy-Paste Prompts' blocks add padding. Fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than level 4, since nearly every phase carries this over-explanation; not level 2 because nothing is concept-tutorial fluff and the code examples are dense.

3 / 5

Actionability

Substantial executable code: the plugin header, `register_post_meta` with `show_in_rest`, the `wp_ai_client_prompt` save_post handler, full Abilities API registration with input/output schemas, and `register_block_type` with render_callback are all copy-paste ready. Falls short of 5 on minor gaps — the DataViews example calls an undefined `handleViewChange`, the block.json workflow is described in comments rather than shown, and the phase 'Actions' lists remain abstract direction. Above level 3 because the code is real, not pseudocode, and covers the common cases.

4 / 5

Workflow Clarity

Nine phases are clearly sequenced (setup through testing) with a final Quality Gates and compatibility checklist, but explicit validation checkpoints are missing inside the phases — the sequence is present yet checkpoints are implicit. The rubric caps workflow clarity at 3 for destructive/batch operations without validation: Phase 5 includes CRUD and 'data upgrade routines' (destructive, batch) with no verify-after-write or rollback/re-validate loop, so the cap applies even though the phase ordering itself would merit a 4.

3 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so the entire ~490-line skill is one monolithic file. Section headers keep it navigable (above level 2's 'minimal structure'), and the content is on-topic (above level 2's clearly-misplaced inlining), but the large WP 7.0 feature code examples (AI Connector, Abilities API, PHP-only blocks) and checklists would be more discoverable split into one-level-deep reference files — matching level 3's 'some structure but could be better organized; content that should be separate is inline'.

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.

A specific, well-scoped description with good natural trigger terms and a distinct plugin-development niche. Its main defect is the missing 'when to use' clause — the description says what the workflow covers but never tells Claude when to invoke it, which caps completeness.

Suggestions

Append an explicit trigger clause, e.g., 'Use when creating or extending WordPress plugins, building plugin admin interfaces or REST endpoints, or integrating WordPress 7.0 AI/collaboration features.'

Add one or two action verbs to convert feature nouns into expected behaviors (e.g., 'Builds plugin architecture, registers hooks and REST endpoints, and implements WordPress 7.0...') to lift specificity from 4 toward 5.

Include common user phrasings like 'custom plugin', 'build a WordPress plugin', or 'WP plugin' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description lists several specific capabilities — 'plugin architecture, hooks, admin interfaces, REST API, security best practices' plus named WordPress 7.0 features ('Real-Time Collaboration, AI Connectors, Abilities API, DataViews, and PHP-only blocks') — with only minor gaps. It sits above level 3 ('1-2 concrete actions') on breadth and specificity of the nouns, but below level 5 because the only action verb is the generic 'covering' — the items are domains/features rather than concrete actions a user can expect performed.

4 / 5

Completeness

The 'what' is clear and specific (a plugin development workflow covering enumerated areas and WP 7.0 features), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3, and the anchor at 3 ('clear what but when missing or only weakly implied') fits exactly — the 'when' is entirely absent, not just implicit, so it does not fall to 2 given the strong 'what'.

3 / 5

Trigger Term Quality

Strong natural terms: 'WordPress plugin development', 'plugin', 'hooks', 'admin interfaces', 'REST API', 'security', 'WordPress 7.0' — phrases a user would plausibly say when they need this skill. Below level 5 because common variations are missing (e.g., 'WP plugin', 'build a plugin', 'custom plugin'); above level 3 because coverage across the domain is broad and multi-word natural, not just one or two generic keywords.

4 / 5

Distinctiveness Conflict Risk

'WordPress plugin development' is a clear niche with plugin-specific triggers (hooks, plugin header, Abilities API registration) that would not fire for unrelated skills. It stays at 4 rather than 5 because the body lists closely related bundles (`wordpress`, `wordpress-theme-development`, `wordpress-woocommerce`) whose broader triggers ('WordPress', 'admin interface', 'REST API') overlap with this description, creating minor conflict risk with a general WordPress skill.

4 / 5

Total

15

/

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

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

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.