CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wordpress-woocommerce-development

Use when building or customizing WooCommerce stores: product configuration, payment gateways, shipping, checkout flow, custom product types, order automation via the Abilities API, or store performance. Do not use for general theme or plugin work; use wordpress-theme-development or wordpress-plugin-development.

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 highly actionable with concrete, mostly executable PHP covering setup through testing, and the phase structure with quality gates gives a clear workflow. Its main weaknesses are token inefficiency from repeated warnings and scattered version-specific details, and the absence of any progressive disclosure — everything, including very long code samples, lives inline in SKILL.md.

Suggestions

Consolidate the HPOS and Real-Time-Collaboration warnings into a single section and reference it from the phases, instead of repeating them in Phases 1, 7, and 8 and the features list.

Move the long code samples (Abilities API registration, AI Q&A AJAX handler, risk scoring) into reference files (e.g. references/abilities-api.md, references/ai-examples.md) and keep short key snippets inline.

Gather version/date-sensitive details (WordPress 7.1.4 release date, PHP requirements) into one version-notes or deprecated section, and define or stub the helper functions used in snippets (`my_store_order_velocity()`, `$cart_key`) so examples are fully executable.

DimensionReasoningScore

Conciseness

The ~640-line body repeats the same warnings across sections (the HPOS "never use get_posts" warning appears in three places and the "Real-Time Collaboration did not ship" note in four), and time-sensitive version/date details ("WordPress 7.1.4 'Mary Lou' (August 19, 2026)", PHP version minimums) are scattered rather than isolated in a deprecated/version section, which the rubric penalizes. Most content otherwise earns its place, so this sits at the mostly-efficient-but-could-be-tightened anchor rather than lower.

3 / 5

Actionability

The body provides extensive, largely copy-paste-ready PHP (hook registrations, Abilities API registration with schemas, CRUD order queries, a PHPUnit test), with only minor gaps — snippets reference undefined helpers like `my_store_order_velocity()`, `$cart_key`, and `$redacted_prompt` without definitions. This matches the mostly-executable anchor with minor gaps rather than the fully-executable top anchor.

4 / 5

Workflow Clarity

Eight clearly sequenced phases each with action lists, plus explicit validation via the Phase 8 testing checklist, Quality Gates, a manual QA checklist for AI features, and the instruction to verify order queries with compatibility mode disabled. It falls short of the top anchor because some validation steps are stated as bare actions ("Performance testing", "Check mobile experience") without how-to or a fix-and-retry loop.

4 / 5

Progressive Disclosure

The body has clear section headers and a "Related skills" list, but no bundle files exist and large blocks that clearly belong in reference files are inlined (a ~100-line Abilities API registration sample, a ~60-line AI Q&A AJAX handler, and the full risk-scoring implementations). This matches the some-structure-but-inline-heavy anchor; it is not a 2 because headers and navigation within the page are well organized.

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.

A strong, well-scoped description with explicit use-when triggers, a concrete capability list, and clear disambiguation from related WordPress skills. Its only gap is missing a few natural synonyms (e.g. "e-commerce store", "online store") that users might use instead of "WooCommerce".

DimensionReasoningScore

Specificity

The description lists multiple concrete capability areas — "product configuration, payment gateways, shipping, checkout flow, custom product types, order automation via the Abilities API, or store performance" — giving comprehensive coverage of the skill's scope, matching the top anchor.

5 / 5

Completeness

It explicitly answers both "what" (building or customizing WooCommerce stores across the listed areas) and "when" ("Use when building or customizing WooCommerce stores..."), plus negative trigger guidance — matching the anchor requiring explicit what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("WooCommerce stores", "payment gateways", "shipping", "checkout flow", "store performance") that users would readily say, but common synonyms like "online store", "e-commerce", or "shop" are missing, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The WooCommerce niche is distinct and the description actively disambiguates from sibling skills ("Do not use for general theme or plugin work; use wordpress-theme-development or wordpress-plugin-development"), minimizing wrong-skill triggering.

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/pro-skills-repo-administraktor

Path

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