AB ecwid
Ecwid REST API v3 integration for managing e-commerce store data including products, orders, customers, categories, discount coupons, promotions, abandoned carts, and store profile. Use when the user wants to interact with their Ecwid online store.
As a process B 76/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5438 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 76/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 21 mutating operations with no state check
- 40Consistency. Frontmatter name (ecwid) differs from the folder (ecwid-ecommerce)
- 65Failures and branches. 3 branches
- 70Execution cost. Instruction body is 5438 tokens
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Progress reporting. Reports progress
- 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 248: enough signal without eating the budget
- +4Structure: 55 headings
- +3Step-by-step instructions: 11 items
- +3Output format is stated explicitly
- +4Has examples (25 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.
External checks
ClawHub: clean
This is a documentation-only Ecwid API skill with expected store-token access; the main caution is that order, customer, and cart queries can expose personal customer data.
LLM: benign (high) · VirusTotal: · 29 May 2026