woocommerce
WooCommerce REST API - products, orders, customers, webhooks
48
37%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/woocommerce/SKILL.mdQuality
Discovery
32%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 the domain (WooCommerce REST API) and lists key resource types, but reads more like a topic list than a functional skill description. It lacks concrete actions, a 'Use when...' clause, and natural trigger term variations that would help Claude reliably select this skill.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user needs to interact with a WooCommerce store via its REST API, including creating/updating products, managing orders, or configuring webhooks.'
Replace the bare noun list with concrete actions, e.g., 'Creates and updates products, retrieves and processes orders, manages customer records, and configures webhooks via the WooCommerce REST API.'
Include additional natural trigger terms users might say, such as 'WooCommerce store', 'e-commerce API', 'shop inventory', 'WooCommerce integration', or 'online store'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (WooCommerce REST API) and lists key resource areas (products, orders, customers, webhooks), but does not describe concrete actions like 'create products', 'process orders', or 'manage webhooks'. | 2 / 3 |
Completeness | Provides a partial 'what' (WooCommerce REST API resources) but completely lacks any 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also weak, so this scores 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', 'e-commerce', 'shop', 'inventory', or 'payment'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'WooCommerce REST API' is fairly specific and distinguishes it from generic e-commerce or API skills, but without concrete actions it could overlap with general WooCommerce or REST API skills. | 2 / 3 |
Total | 7 / 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.
The skill provides highly actionable, executable code examples covering the full WooCommerce REST API surface, which is its primary strength. However, it is far too verbose - essentially a full API reference document rather than a concise skill that teaches Claude what it doesn't already know. The content would benefit enormously from splitting into a concise overview with references to detailed sub-files, and from removing standard REST patterns Claude can infer.
Suggestions
Reduce the main file to core patterns (auth setup, one CRUD example, webhook verification, error handling) and move product/order/customer/coupon/report details to separate reference files linked from the overview.
Remove duplicate TypeScript/Python examples - since the header says to load with either typescript.md or python.md, pick one language for inline examples or split by language file.
Add explicit validation checkpoints for destructive operations like deleteProduct(force=true) and batch operations, e.g., 'verify product exists before deletion' or 'confirm order count before bulk status update'.
Cut explanations of standard concepts like what order statuses mean or what pagination headers are - Claude knows REST API conventions and can reference the linked docs for details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~500+ lines, providing dual TypeScript/Python examples for nearly every operation, full CRUD for products/orders/customers/coupons/reports/categories/tags, and extensive boilerplate code. Much of this is standard REST API usage that Claude already knows - the skill essentially reproduces the WooCommerce API documentation rather than distilling what's unique or non-obvious. | 1 / 3 |
Actionability | All code examples are concrete, executable, and copy-paste ready with proper imports, environment variable usage, and complete function signatures. The webhook verification, error handling, and pagination examples are particularly well-done with real library calls. | 3 / 3 |
Workflow Clarity | The prerequisites and checklist sections provide a reasonable setup workflow, and the variable product creation shows a clear two-step process. However, there are no validation checkpoints for destructive operations (delete product with force=true), no verification steps after creating orders/products, and no feedback loops for error recovery beyond the generic error handler. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files for detailed API coverage. The skill header mentions 'Load with: base.md + (typescript.md or python.md)' but then includes both TypeScript and Python inline throughout. Categories, tags, coupons, reports, and pagination could all be in separate reference files, keeping the main skill focused on core patterns. | 1 / 3 |
Total | 7 / 12 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (782 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
d4ddb03
- 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.