CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wordpress-woocommerce-development

WooCommerce store development workflow covering store setup, payment integration, shipping configuration, customization, and WordPress 7.0 features: AI connectors, DataViews, and collaboration tools.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wordpress-woocommerce-development/SKILL.md

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

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 body delivers genuinely executable, novel WP 7.0 + WooCommerce code in a clearly phased workflow with a testing phase and quality gates, but it is a monolithic file with redundant feature restatements, one broken hook callback name, and no reference files to offload the large code examples. Splitting code into reference files and de-duplicating the feature lists would improve both conciseness and disclosure.

Suggestions

Move the large code examples (Abilities API registration, AJAX product Q&A) into files under references/ and link them from the phases, keeping SKILL.md as a lean overview.

Fix the non-executable snippet: the add_action callback 'generate_ai_description' does not match the defined function name 'generate_ai_product_description'.

De-duplicate the feature material repeated across the 'WordPress 7.0 + WooCommerce Features' section, per-phase bullets, and the 'AI Use Cases' section into one location.

DimensionReasoningScore

Conciseness

The code samples for novel WP 7.0 APIs (wp_ai_client_prompt, Abilities API) earn their tokens, but the same feature material is restated three times ('WordPress 7.0 + WooCommerce Features' list, per-phase bullets, and 'WooCommerce + WordPress 7.0 AI Use Cases'), the function_exists guard boilerplate repeats in every block, and pervasive 'WP 7.0' version references are time-sensitive without a deprecated-patterns section. Mostly efficient but needs tightening, so anchor 3 rather than the minor-trim anchor 4.

3 / 5

Actionability

Concrete, mostly complete PHP throughout (AI description generation, fraud check, Abilities API registration with JSON schemas, nonce-verified AJAX handler), but one snippet is not executable as written: add_action('woocommerce_new_product', 'generate_ai_description', 10, 2) references a callback that does not match the defined function name generate_ai_product_description, and the shipping recommender only handles the 'express' case. Mostly executable with minor gaps, so anchor 4 rather than fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Eight clearly sequenced phases with ordered actions, a dedicated Phase 8 testing step ('Test checkout flow', 'Verify AI features work'), and a Quality Gates checklist ('Checkout flow working', 'Payments processing') providing explicit checkpoints. Minor gaps: validation is implicit within phases and there is no test -> fix -> retest feedback-loop guidance, keeping it at anchor 4 rather than anchor 5; the destructive/batch cap does not apply since operations are not destructive.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so everything is inlined in a ~630-line monolith where large code blocks (the ~100-line Abilities API section, the ~60-line AJAX handler) clearly belong in separate reference files. Good section headers give real structure, so anchor 3 ('some structure but content that should be separate is inline') rather than anchor 4 or the minimal-structure anchor 2; the sub-50-line simple-skill exception does not apply.

3 / 5

Total

14

/

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 states a clear, specific 'what' with well-chosen domain keywords, but omits any explicit 'Use when...' trigger guidance, which both caps completeness and weakens its function as a routing signal. Adding a trigger clause and common synonyms (e-commerce store, online store, checkout) would round it out.

Suggestions

Append an explicit trigger clause, e.g. 'Use when building or customizing WooCommerce stores, integrating payment gateways, or implementing WordPress 7.0 AI features.'

Add natural synonyms users would say: 'e-commerce store', 'online store', 'checkout', 'WordPress shop'.

Mention testing and store optimization to align description coverage with the body's Phase 7/8 content.

DimensionReasoningScore

Specificity

Names the domain and several concrete action areas ('store setup, payment integration, shipping configuration, customization') plus specific feature surfaces ('AI connectors, DataViews, and collaboration tools'), but coverage has minor gaps (testing and optimization phases in the body are absent from the description). Fits the 'several specific actions; minor gaps' anchor rather than the comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clear (a WooCommerce store development workflow with listed coverage areas), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. Clear 'what' with 'when' missing exactly matches the anchor-3 example.

3 / 5

Trigger Term Quality

Good keywords users would naturally say ('WooCommerce', 'WordPress 7.0', 'payment integration', 'shipping'), but common synonyms are missing — no 'e-commerce store', 'online store', 'checkout', or 'WordPress shop'. Good coverage with a few natural terms missing, so anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The WooCommerce + WordPress 7.0 niche is well-scoped with distinct triggers, but 'customization' creates minor overlap risk with generic WordPress theme/plugin development skills. Mostly distinct with minor overlap, so anchor 4 rather than the minimal-conflict anchor 5 or the still-overlapping anchor 3.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/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.