woocommerce

WooCommerce REST API - products, orders, customers, webhooks

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/woocommerce/SKILL.md

Quality

Content

58%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 skill is highly actionable with executable code across all major WooCommerce resources, but it is a monolithic inline reference with no progressive disclosure or bundle files, and destructive/batch workflows lack explicit validation feedback loops.

Suggestions

Split the large per-resource code references into separate files under references/ (e.g., products.md, orders.md, webhooks.md) and link to them one level deep from SKILL.md.

Add explicit validation/verification checkpoints to destructive and batch workflows (e.g., verify a product exists before force-deleting; confirm pagination totals before bulk mutations).

Trim repeated CRUD boilerplate and redundant auth/setup blocks to reduce token cost while preserving the executable examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material, but at ~770 lines it inlines a large amount of API reference code (Products, Orders, Customers, Webhooks, etc.) that repeats similar CRUD patterns and could be tightened or moved to reference files.	3 / 5
Actionability	Nearly every section provides copy-paste-ready, executable TypeScript and Python code with real endpoint paths, parameters, and env-var usage, covering the common cases comprehensively.	5 / 5
Workflow Clarity	Sequences are present and there are checklists and an error-handling/retry example, but batch and destructive operations (delete with force, bulk pagination, webhook handling) lack explicit validate-then-proceed feedback loops, capping this at 3 per the rubric.	3 / 5
Progressive Disclosure	There are no references/, scripts/, or assets/ bundle files, and the entire API reference is inlined as a monolithic ~770-line wall of code that clearly belongs in separate reference files, with no one-level-deep navigation signaled.	2 / 5
	Total	13 / 20 Passed

Description

50%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 identifies a clear niche (WooCommerce REST API) and lists key resources, but it reads as a capability inventory rather than action-oriented guidance and lacks an inline 'Use when' trigger clause.

Suggestions

Add concrete actions per resource (e.g., 'list, create, update, and delete products and orders') instead of just listing resource names.

Append an explicit 'Use when' clause to the description itself, such as 'Use when integrating with WooCommerce stores or managing WooCommerce products, orders, customers, or webhooks.'

Include natural synonyms users might say, like 'WordPress store', 'WooCommerce orders', or 'WC API', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (WooCommerce REST API) and several concrete resources (products, orders, customers, webhooks), but only lists resource categories rather than specific actions like create, list, update, or verify.	3 / 5
Completeness	It has a clear 'what' (WooCommerce REST API resources), but the explicit 'when' trigger guidance is in the separate 'when-to-use' field rather than the description itself, so the description alone has no Use-when clause.	3 / 5
Trigger Term Quality	'WooCommerce stores' and 'integrating with WooCommerce' are relevant terms, but it lacks common natural variations and synonyms a user might say (e.g., 'WooCommerce orders', 'WordPress store', 'WC API').	3 / 5
Distinctiveness Conflict Risk	'WooCommerce REST API' is a clear niche with distinct triggers and minimal overlap risk with other skills; only minor breadth keeps it from a 5.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/woocommerce/SKILL.md
Commit: abc600e

Reviewed: 7 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.