woocommerce

WooCommerce REST API - products, orders, customers, webhooks

Quality

41%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/woocommerce/SKILL.md

Quality

Discovery

40%

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 identifies a clear domain (WooCommerce REST API) and lists key resource areas, giving it good distinctiveness. However, it lacks concrete action verbs describing what the skill does and entirely omits a 'Use when...' clause, making it incomplete for skill selection among many options.

Suggestions

Add concrete actions for each resource area, e.g., 'Create, update, and retrieve products; process and manage orders; manage customer records; configure webhooks for WooCommerce stores.'

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to interact with a WooCommerce store via its REST API, mentions WooCommerce, ecommerce orders, or online shop management.'

Include common user-facing trigger terms like 'ecommerce', 'online store', 'shop', 'inventory', 'WooCommerce plugin' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (WooCommerce REST API) and lists key resource areas (products, orders, customers, webhooks), but doesn't describe concrete actions like 'create products', 'process orders', or 'manage webhooks'.	2 / 3
Completeness	Only partially addresses 'what' (lists resource areas but no actions) and completely lacks a 'when' clause or any explicit trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'WooCommerce', 'REST API', 'products', 'orders', 'customers', and 'webhooks' that users might naturally mention, but misses common variations like 'WooCommerce store', 'ecommerce', 'shop', 'inventory', or 'payment'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'WooCommerce REST API' is a clear, specific niche that is unlikely to conflict with other skills. The domain is well-defined and distinct.	3 / 3
	Total	8 / 12 Passed

Implementation

42%

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

This skill is essentially a reproduction of the WooCommerce REST API documentation with executable code examples in two languages. While the code is high-quality and actionable, the skill is far too verbose for a context-window-conscious format — it explains standard REST API patterns Claude already knows and duplicates everything in Node.js and Python. The content desperately needs to be split into separate files with a lean overview in the main SKILL.md.

Suggestions

Reduce the main SKILL.md to a concise overview (~50-80 lines) covering authentication setup, base URL, and one example per resource type, then split detailed CRUD operations into separate files (e.g., PRODUCTS.md, ORDERS.md, WEBHOOKS.md).

Pick one primary language for examples instead of duplicating every snippet in both Node.js and Python — or relegate the second language to a separate reference file.

Remove standard patterns Claude already knows (basic CRUD, pagination, generic error handling) and focus on WooCommerce-specific gotchas, edge cases, and non-obvious behaviors.

Add explicit validation steps for multi-step workflows like variable product creation (e.g., verify parent product exists before creating variations, check variation count matches expected).

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~500+ lines. Massive amounts of boilerplate code that Claude already knows how to write (basic CRUD operations, standard REST API patterns). The Node.js and Python examples are duplicated for nearly every section. Concepts like pagination, error handling, and environment variables are standard patterns that don't need this level of detail. The skill essentially reproduces API documentation rather than providing targeted, novel guidance.	1 / 3
Actionability	All code examples are fully executable and copy-paste ready with proper imports, real library usage, and complete function signatures. Both Node.js and Python examples are provided with concrete parameters, and webhook verification includes complete working handlers.	3 / 3
Workflow Clarity	The checklists at the end provide some workflow structure, and the prerequisites section sequences setup steps. However, there are no validation checkpoints within the actual API operations (e.g., no guidance on verifying a product was created correctly, no error recovery workflow for batch operations, no explicit 'verify then proceed' patterns for destructive operations like delete).	2 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files. Everything is inline — products, orders, customers, webhooks, coupons, reports, pagination, error handling, categories, and tags are all in one massive document. This content would benefit enormously from being split into separate reference files (e.g., PRODUCTS.md, ORDERS.md, WEBHOOKS.md) with a concise overview in the main skill.	1 / 3
	Total	7 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (781 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: alinaqi/claude-bootstrap
Commit: 65efb33

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.