woocommerce
WooCommerce REST API - products, orders, customers, webhooks
40
41%
Does it follow best practices?
Impact
—
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
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 niche (WooCommerce REST API) and lists relevant resource types, making it distinctive. However, it reads more like a keyword list than a proper description—it lacks concrete actions (what does it do with products/orders?) and has no 'Use when...' clause to guide skill selection. Adding action verbs and explicit trigger guidance would significantly improve its effectiveness.
Suggestions
Add concrete actions for each resource, e.g., 'Create, update, and retrieve WooCommerce products, process and manage orders, handle customer data, and configure webhooks via the REST API.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to interact with a WooCommerce store programmatically, manage ecommerce data, or integrate with WooCommerce endpoints.'
Include common user-facing synonyms like 'ecommerce', 'online store', 'shop', 'inventory', and 'WooCommerce plugin' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (WooCommerce REST API) and lists resource types (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 nouns without actions) and completely lacks a 'when' clause or any explicit trigger guidance, which per the rubric caps this at 2 maximum—but since the 'what' is also weak, it scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'WooCommerce', 'REST API', 'products', 'orders', 'customers', and 'webhooks' that users might naturally say, but misses common variations like 'WooCommerce store', 'ecommerce', 'shop', 'inventory', or 'payment'. | 2 / 3 |
Distinctiveness Conflict Risk | WooCommerce REST API is a very specific niche that is unlikely to conflict with other skills. The combination of 'WooCommerce' and 'REST API' with specific resource types creates a clear, distinct identity. | 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.
The skill is a comprehensive WooCommerce API reference with excellent actionability—every code example is executable and well-structured. However, it is severely over-long and monolithic, essentially dumping an entire API reference into a single file without progressive disclosure. Much of the content (standard CRUD patterns, basic Express handlers, environment variable setup) is knowledge Claude already possesses, making the token cost disproportionate to the unique value added.
Suggestions
Reduce content by 60-70%: remove dual-language examples (pick one primary), eliminate standard CRUD boilerplate Claude knows, and focus on WooCommerce-specific gotchas (permalink requirement, variable product two-step creation, webhook signature format).
Split into multiple files: keep SKILL.md as a concise overview (~50-80 lines) with links to PRODUCTS.md, ORDERS.md, WEBHOOKS.md for detailed examples.
Add validation checkpoints for destructive operations: e.g., before deleting products, verify the product exists and log the action; before bulk updates, confirm counts match expectations.
Remove explanations of concepts Claude already knows (what order statuses mean, how environment variables work, basic error handling patterns) and replace with a terse reference table or omit entirely.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Provides dual Node.js/Python examples for nearly every operation, includes extensive boilerplate Claude already knows (basic CRUD patterns, Express route handlers, environment variable setup), and repeats similar patterns (list/get/create/update/delete) across products, orders, customers without adding novel insight. The authentication section alone appears three times in slightly different forms. | 1 / 3 |
Actionability | All code examples are fully executable with proper imports, real library usage, and copy-paste ready patterns. Covers concrete operations including webhook signature verification, pagination with headers, error handling with retry logic, and variable product creation with step-by-step API calls. | 3 / 3 |
Workflow Clarity | The checklist at the end provides a good pre-integration sequence, and the variable product creation shows a clear two-step process. However, there are no validation checkpoints for destructive operations (delete product, batch updates), no feedback loops for error recovery beyond the generic error handler, and the overall document reads as a reference catalog rather than a guided workflow. | 2 / 3 |
Progressive Disclosure | Monolithic wall of content with no references to external files despite the massive size. Everything from basic auth setup to webhook verification to reports is inlined. This would benefit enormously from splitting into separate files (e.g., PRODUCTS.md, ORDERS.md, WEBHOOKS.md) with the SKILL.md serving as a concise overview with links. | 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 (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
7e5f7a2
- 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.