CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

48

Quality

52%

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/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

38%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill attempts to cover an extremely broad scope (8 workflow phases plus WP 7.0 AI features) in a single monolithic file, resulting in significant verbosity without proportional actionability. The code examples are reasonably well-written PHP but many reference speculative APIs, and the non-code sections are mostly vague checklists. The workflow structure provides sequencing but lacks the validation checkpoints and error recovery needed for operations involving payments and store configuration.

Suggestions

Split the massive code examples (Abilities API, AI product Q&A, fraud detection) into separate reference files and link to them from the main skill, keeping only the most essential 1-2 code snippets inline.

Replace vague action lists ('Configure CDN', 'Set up tax rules') with specific WP-CLI commands or concrete configuration steps, or remove them entirely since Claude knows how to do basic WooCommerce setup.

Add explicit validation checkpoints between phases, especially after payment integration (test charge), shipping configuration (verify rate calculation), and store setup (verify WooCommerce status via wp wc system_status).

Remove or drastically condense the WordPress 7.0 feature overview sections and 'AI Use Cases' list—these are descriptive padding that don't provide actionable guidance.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~400+ lines. It extensively explains WP 7.0 features Claude doesn't need described (DataViews, collaboration, admin refresh), includes lengthy code blocks for speculative features (AI fraud detection via LLM prompt is questionable practice), and lists many vague bullet points ('Configure CDN', 'Set up lazy loading') without actionable detail. The WordPress 7.0 feature lists at the top and the 'AI Use Cases' section near the bottom are pure padding.

2 / 5

Actionability

The code examples are mostly executable PHP and demonstrate real WooCommerce hooks and patterns. However, many 'Actions' sections are just vague checklists ('Install WooCommerce', 'Configure CDN') with no concrete commands or code. The 'Copy-Paste Prompts' are minimal one-liners that delegate to other skills. The AI API usage (wp_ai_client_prompt) references a speculative WordPress 7.0 API that may not exist in this form, reducing practical actionability.

3 / 5

Workflow Clarity

The 8-phase structure provides a clear sequence, and the quality gates checklist at the end is useful. However, there are no validation checkpoints between phases, no error recovery steps, and no feedback loops. Payment integration and shipping configuration are potentially destructive/critical operations that lack verification steps. The phases read more like a table of contents than a guided workflow.

3 / 5

Progressive Disclosure

This is a monolithic ~400+ line file with no bundle files to offload content to. The massive code blocks (especially the Abilities API registration at ~80 lines and the product Q&A handler) should be in separate reference files. References to other skills/bundles exist but are just names without clear navigation. The 'Related Workflow Bundles' section at the end is helpful but insufficient to compensate for the inlined bulk.

2 / 5

Total

10

/

20

Passed

Description

66%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 does a solid job identifying the domain (WooCommerce/WordPress 7.0) and listing specific capability areas, making it reasonably distinctive. Its main weakness is the absence of an explicit 'Use when...' clause, which limits Claude's ability to know precisely when to select this skill. The description also lists topic areas rather than concrete action verbs, slightly reducing specificity.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks about WooCommerce setup, online store development, payment gateways, or WordPress 7.0 features'.

Include common synonyms and related terms such as 'e-commerce', 'online store', 'checkout', 'product catalog', and 'plugins' to improve trigger term coverage.

Rephrase topic areas as concrete actions (e.g., 'Sets up WooCommerce stores, integrates payment gateways, configures shipping rules') for stronger specificity.

DimensionReasoningScore

Specificity

Lists several specific areas: store setup, payment integration, shipping configuration, customization, and WordPress 7.0 features including AI connectors, DataViews, and collaboration tools. Coverage is good but actions are described as topic areas rather than concrete verbs (e.g., 'covering store setup' rather than 'configures stores').

4 / 5

Completeness

The 'what' is reasonably clear — WooCommerce store development covering multiple areas. However, there is no explicit 'when' clause (no 'Use when...' or equivalent trigger guidance), which per the rubric caps this dimension at 3.

3 / 5

Trigger Term Quality

Includes strong natural keywords like 'WooCommerce', 'store', 'payment integration', 'shipping', 'WordPress 7.0', 'AI connectors', 'DataViews'. Missing some common user phrases like 'e-commerce', 'online store', 'checkout', 'product catalog', or 'plugins'.

4 / 5

Distinctiveness Conflict Risk

The combination of WooCommerce + WordPress 7.0 specific features (AI connectors, DataViews) creates a fairly distinct niche. Minor overlap risk with generic WordPress development skills, but the WooCommerce and version-specific focus reduces conflict.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation9 / 11 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

9

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.