SKILLEMALL.ai

AB store-audit

Use when reviewing an online store as a whole — homepage, category pages, channel mix, or trust — e.g. "review my store", "audit my homepage", "Instagram or Google Ads?", "should we say we're a small team", "how should we label recommendations", "carousel or grid", "how do we look more trustworthy", "should we sell on Amazon too". For one product page, use product-page; for cart or checkout, use checkout-ux.

checkout-page/ecommerce-skills Agent Skills author: checkout-page 2 files body ≈ 1 114 tokens Open the sourcegithub.com↗ analyzed 3 d ago

g. "review my store", "audit my homepage", "Instagram or Google Ads?", "should we say we're a small team", "how should we label recommendations", "carousel or…

As a process B 72/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting

AnalyzerCommercetype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
B
72/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    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: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 72/100

    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 1 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 26 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1114 tokens

    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

    • +4Description does not say when NOT to use the skill (false activations)
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 8 example trigger phrases
    • +3Description length 411: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 26 items
    • +3Output format is stated explicitly

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