SKILLEMALL.ai

BC woocommerce

WooCommerce REST API integration with managed OAuth. Access products, orders, customers, coupons, shipping, taxes, reports, and webhooks. Use this skill when users want to manage e-commerce operations, process orders, or integrate with WooCommerce stores. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 8 362 tokens Open the sourcegithub.com analyzed 2 d ago

WooCommerce REST API integration with managed OAuth.

As a process C 53/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, execution cost

IntegrationWordPressCommerceSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
76/100
safety, quality, tests
Safety 60%
75
Quality 40%
78
Run on models
none yet
Process rating
C
53/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 5

✓ No critical or high findings

Medium and low: 5
  • medium Exfiltration net-credential-use SKILL.md:172
    Credential used in a network call (verify the destination is the intended service)
    curl -s -X GET "https://gateway.maton.ai/woocommerce/wp-json/wc/v3/products?per_page=20&status=…" -H "Authorization: Bearer $MATON_API_KEY"
  • medium Exfiltration net-credential-use SKILL.md:205
    Credential used in a network call (verify the destination is the intended service)
    curl -s -X GET "https://gateway.maton.ai/woocommerce/wp-json/wc/v3/products/123" -H "Authorization: Bearer $MATON_API_KEY"
  • medium Exfiltration net-credential-use SKILL.md:231
    Credential used in a network call (verify the destination is the intended service)
    curl -s -X POST "https://gateway.maton.ai/woocommerce/wp-json/wc/v3/products" -H "Content-Type: application/json" -H "Authorization: Bearer $MATON_API_KEY" -d '{"name": "Premium Widget", "type": "simp
  • medium Exfiltration net-credential-use SKILL.md:243
    Credential used in a network call (verify the destination is the intended service)
    curl -s -X PUT "https://gateway.maton.ai/woocommerce/wp-json/wc/v3/products/123" -H "Content-Type: application/json" -H "Authorization: Bearer $MATON_API_KEY" -d '{"regular_price": "24.99", "sale_pric
  • medium Exfiltration net-credential-use SKILL.md:462
    Credential used in a network call (verify the destination is the intended service)
    curl -s -X GET "https://gateway.maton.ai/woocommerce/wp-json/wc/v3/orders?status=…&per_page=50" -H "Authorization: Bearer $MATON_API_KEY"

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 8362 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 53/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 46 mutating operations with no state check
  • 40Execution cost. Instruction body is 8362 tokens: crowds the task out of the window
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 136 steps
  • 100Consistency. Name and required fields are in place
  • low 11 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +2Single-language instructions
  • +3Description length 352: enough signal without eating the budget
  • +4Structure: 123 headings
  • +3Step-by-step instructions: 136 items
  • +3Output format is stated explicitly
  • +4Has examples (106 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.