CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wordpress

Use when building, extending, auditing, or modernizing WordPress sites end to end: themes, plugins, WooCommerce, performance, security hardening, or WordPress 7.0 features (AI Client, Abilities API, PHP-only blocks, DataViews). Use as the entry point that routes to the three focused WordPress skills. Do not use for non-WordPress PHP, or front-end work with no WordPress involvement.

Quality

81%

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

63%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 dense with genuinely valuable, version-current WordPress 7.0 and MCP material backed by mostly executable code and a clearly sequenced eight-phase workflow with explicit quality gates. Its weaknesses are padding from generic checklists and boilerplate structure trees, a stub WooCommerce example, and the absence of any progressive disclosure — everything lives inline in one large file despite the skill claiming to be a thin routing entry point.

Suggestions

Trim or remove content Claude already knows — the theme and plugin directory structure trees, the generic security checklist ('Strong passwords enforced', 'Regular backups configured'), and boilerplate phase action lists — keeping only the WordPress 7.0-specific deltas.

Since the description positions this skill as an entry point routing to wordpress-theme-development, wordpress-plugin-development, and wordpress-woocommerce-development, move the detailed theme/plugin/WooCommerce sections into those skills (or reference files) and keep only routing guidance plus the 7.0-specific notes inline.

Replace the empty WC_Product_Custom stub with a working minimal custom product type example (e.g., overriding get_type() and get_price() and registering the product type via the woocommerce_product_type filter), and fill in the '[...]' labels placeholder in register_post_type.

DimensionReasoningScore

Conciseness

The WordPress 7.0 specifics (RTC removal, AI Client, Abilities API hooks), the MCP integration section, and the code examples earn their tokens, but generic boilerplate Claude already knows is inlined — theme/plugin directory structure trees, stock action lists ('Set up version control', 'Configure wp-config.php for development'), and standard security/performance checklists ('Strong passwords enabled', Core Web Vitals thresholds). This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the level-2 anchor because the majority of the content is version-current, post-cutoff WordPress 7.0 material Claude does not already know.

3 / 5

Actionability

Mostly executable, copy-paste-ready guidance: register_post_meta with show_in_rest, fluent wp_ai_client_prompt() chains with a JSON-schema example, full Abilities API registration including the handler with input validation and WP_Error returns, permission_callback warnings, and concrete MCP server JSON configs. It falls short of the level-5 anchor because the WooCommerce product-type example is an empty stub ('class WC_Product_Custom extends WC_Product { // Custom product implementation }') and register_post_type uses a literal '[...]' placeholder for labels.

4 / 5

Workflow Clarity

Eight phases are clearly sequenced (setup through deployment) with explicit checkpoints — 'Verify WordPress.org Plugin Check (wp plugin check) with 0 errors and 0 warnings', a per-phase Quality Gates checklist ('Before moving to next phase, verify: ...'), and a dedicated testing phase. It stops short of the level-5 anchor because there are no error-recovery feedback loops (no guidance on what to do when a quality gate or plugin check fails, only that it must pass).

4 / 5

Progressive Disclosure

The body is a monolithic ~570-line file with no bundle files (no references/, scripts/, or assets/ exist) and no one-level-deep reference files of its own, despite the frontmatter describing it as 'the entry point that routes to the three focused WordPress skills'. Header structure is good, but detailed theme, plugin, and WooCommerce content that belongs in those focused skills is duplicated inline, fitting the anchor 'some structure but could be better organized; content that should be separate is inline' rather than the level-4 anchor, which requires references mostly pointing to separate files.

3 / 5

Total

14

/

20

Passed

Description

92%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 strong: it explicitly states both what the skill is (an entry point orchestrating three focused WordPress skills) and when to use it, with concrete trigger phrases and explicit negative triggers to prevent misfiring. The only weakness is modest synonym coverage for natural user phrasings like 'WP', 'store setup', or 'caching'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('building, extending, auditing, or modernizing WordPress sites end to end') across named domains including specific 7.0 APIs ('AI Client, Abilities API, PHP-only blocks, DataViews'), giving comprehensive coverage with no meaningful gaps, matching the top anchor rather than the 'minor gaps' level-4 anchor.

5 / 5

Completeness

Both 'what' ('Use as the entry point that routes to the three focused WordPress skills' covering themes, plugins, WooCommerce, performance, security) and 'when' ('Use when building, extending, auditing, or modernizing...') are explicitly stated with concrete trigger phrases and negative triggers ('Do not use for non-WordPress PHP, or front-end work with no WordPress involvement'), clearly matching the top anchor rather than the level-4 anchor where the 'when' could be more explicit.

5 / 5

Trigger Term Quality

Natural terms users would say are well covered ('WordPress', 'themes', 'plugins', 'WooCommerce', 'performance', 'security hardening', 'WordPress 7.0'), but a few common variations are missing (e.g., 'WP', 'store/e-commerce setup', 'caching/site speed'), fitting the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive-synonyms level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clear WordPress-only niche is combined with explicit conflict avoidance — negative triggers ('Do not use for non-WordPress PHP, or front-end work with no WordPress involvement') and explicit routing ('routes to the three focused WordPress skills') — giving minimal conflict risk, matching the 'clear niche with distinct triggers' top anchor.

5 / 5

Total

19

/

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 (573 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

administrakt0r/pro-skills-repo-administraktor

Path

skills/wordpress-skills/wordpress/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.