Tessl • The package manager for agent skills

Blog Docs Log inGet started

SkillPublic

woocommerce

WooCommerce REST API - products, orders, customers, webhooks

Quality

73%

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

72%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 — nearly every section is complete, executable code with concrete parameter values — and it avoids padding. Its weaknesses are structural: everything lives inline in one large file with no progressive disclosure, and workflows involving destructive or batch operations lack explicit validation checkpoints.

Suggestions

Split the per-resource API reference (orders, customers, webhooks, coupons, reports) into one-level-deep reference files (e.g. references/orders.md) and keep SKILL.md as a concise overview with clearly signaled links.

Add explicit validation before destructive operations, e.g. fetch and verify the product/order before force-deleting, and confirm total counts after batch pagination loops.

Remove the duplicated Node.js and Python client setup blocks between 'API Basics' and 'Installation' to tighten token usage.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code, tables, and checklists with no explanations of concepts Claude already knows, but the Node.js and Python client setup blocks are fully duplicated between 'API Basics' and 'Installation', which is more than trivial trim.	4 / 5
Actionability	Copy-paste ready, executable code covers the common cases: auth setup, product/order/customer CRUD, variable products, webhook creation with HMAC signature verification in both TypeScript and Python, pagination via the X-WP-TotalPages header, and error handling with a 429 retry.	5 / 5
Workflow Clarity	A prerequisites sequence and before-integration/testing checklists provide rough sequencing, but operations include destructive deletes (force: true permanently deletes) and batch pagination loops with no inline validation checkpoints — the destructive/batch cap limits workflow clarity to 3.	3 / 5
Progressive Disclosure	The ~770-line file has clear section headers but no bundle files at all; the full API reference for every resource (products, orders, customers, webhooks, coupons, reports) is inlined in SKILL.md rather than split into one-level-deep reference files, matching the anchor for content that should be separate being inline.	3 / 5
	Total	15 / 20 Passed

Description

65%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 is distinct and reasonably specific about its domain and resource scope, but it omits any 'Use when...' trigger guidance and uses noun lists instead of concrete action verbs. Adding an explicit trigger sentence and action-oriented phrasing would raise both completeness and specificity.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when integrating with WooCommerce stores, managing store products/orders/customers, or handling WooCommerce webhooks.'

Rewrite the scope as concrete actions, e.g. 'Create, update, and delete products; process orders; manage customers; verify webhook signatures' instead of the bare noun list.

Add natural synonyms users might say (WordPress store, e-commerce store) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('WooCommerce REST API') plus four concrete resource areas ('products, orders, customers, webhooks'), but lists no action verbs — the enumerated nouns give more scope than anchor 2's minimal/generic actions, yet it lacks the several specific actions of anchor 4.	3 / 5
Completeness	The description clearly answers 'what' (WooCommerce REST API for products, orders, customers, webhooks) but contains no 'Use when...' clause or equivalent trigger guidance; the separate frontmatter 'when-to-use' field is not part of the description, so completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say such as 'WooCommerce', 'orders', 'customers', and 'webhooks', but misses common synonyms and variations like 'WordPress', 'store', or 'e-commerce' that anchor 5 requires.	4 / 5
Distinctiveness Conflict Risk	'WooCommerce REST API' carves out a clear niche with distinct triggers (WooCommerce, REST API, the four resource types) and minimal risk of firing for an unrelated skill.	5 / 5
	Total	15 / 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/maggy
Path: skills/woocommerce/SKILL.md
Revision: 55aabe2

Reviewed: 26 days ago

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.

woocommerce

Table of Contents

Is this your skill?