woocommerce

WooCommerce REST API - products, orders, customers, webhooks

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

65%

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, packed with executable bilingual code examples, but it is a long monolithic inline reference with duplicated setup sections and no progressive disclosure to offload detail, and its workflows lack explicit validation checkpoints for destructive and batch operations.

Suggestions

Split the per-resource API reference (products, orders, customers, webhooks, coupons, reports) into one-level-deep reference files and keep SKILL.md as a concise overview with signaled links, raising progressive disclosure.

Consolidate the duplicated auth/client setup (API Basics vs Installation) into a single section to remove redundancy and tighten conciseness.

Add an explicit numbered integration workflow with validation checkpoints (e.g., verify credentials with a test call before bulk operations, confirm force-delete intent) to lift workflow clarity above 2.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely terse, executable code with minimal concept-explanation, but the API-client/auth setup is duplicated across "API Basics" and "Installation" (Node and Python each), and ~770 lines of inline reference could be tightened.	2 / 3
Actionability	Provides extensive, executable, copy-paste-ready examples in both Node.js and Python covering products, orders, customers, webhooks, coupons, reports, pagination, and error handling with specific endpoints and fields.	3 / 3
Workflow Clarity	Checklists (Before Integration, Security, Testing) and a 429 retry loop exist, but there is no explicit sequenced end-to-end workflow, and destructive/batch operations (force-delete, order status changes, bulk pagination) lack validation checkpoints, capping the score at 2.	2 / 3
Progressive Disclosure	Sections are well-organized, but the entire ~770-line API reference is inline in SKILL.md with no bundle files or one-level-deep references; the under-50-line exception does not apply, so content that should be split remains inline.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 specific and distinctive, naming a clear platform niche with natural trigger terms, but it states only the "what" inline and relies on a separate when-to-use field for the trigger, leaving completeness short of fully self-contained.

Suggestions

Fold an explicit "Use when..." trigger into the description itself (e.g., "...webhooks. Use when integrating with or migrating data from WooCommerce stores.") so the description field answers both what and when.

Replace the bare resource nouns with concrete action verbs to lift specificity (e.g., "Create and manage products, orders, customers, and webhooks via the WooCommerce REST API").

Mention the additional capabilities the skill actually covers (coupons, reports, categories, pagination) to make the capability list more comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain ("WooCommerce REST API") and enumerates four concrete resource areas ("products, orders, customers, webhooks"), but these are noun-listed resources rather than concrete action verbs, and coverage is not comprehensive (e.g., coupons, reports, categories are absent).	2 / 3
Completeness	The description clearly answers "what" (WooCommerce REST API across four resource areas), but the explicit "when" trigger lives in the separate when-to-use field ("When integrating with WooCommerce stores") rather than inline, so the trigger guidance is only implied within the description field itself.	2 / 3
Trigger Term Quality	"WooCommerce", "products", "orders", "customers", and "webhooks" are exactly the natural terms a user would say when requesting this integration, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	"WooCommerce REST API" is a specific platform niche with a distinctive trigger ("WooCommerce") that is unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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: bb6195f

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.