SKILLEMALL.ai

CF ecommerce-seo

E-commerce SEO audit for online stores (WooCommerce, Shopify, Magento, custom). Covers category / product listing pages (PLP), product detail pages (PDP), faceted navigation and its crawl-budget and duplicate-content traps, pagination, canonicals for variants and filters, out-of-stock / discontinued products, internal linking and breadcrumbs, and Product / Offer / Review / AggregateRating / BreadcrumbList structured data. Use whenever the user runs an online store and asks about product or category page SEO, filter URLs being indexed, product rich results, or thin/duplicate product pages. Trigger on: "e-commerce SEO", "ecommerce SEO", "product page SEO", "category page SEO", "WooCommerce SEO", "Shopify SEO", "faceted navigation", "filter URLs in Google", "product schema", "rich snippets for products", "out of stock SEO", "duplicate product pages". For a single URL use /seo-page; for full-site use /seo-analysis.

nowork-studio/notfair-plugin Claude Code author: nowork-studio MIT 1 file body ≈ 62 tokens Open the sourcegithub.com↗ analyzed 2 d ago

E-commerce SEO audit for online stores (WooCommerce, Shopify, Magento, custom).

As a process F 26/100 · No process to follow — References files that are not bundled: ../../seo/ecommerce-seo/WORKFLOW.md

AnalyzerShopifyWordPressMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
C
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
54
Run on models
none yet
Process rating
F
26/100
No process to follow
References files that are not bundled: ../../seo/ecommerce-seo/WORKFLOW.md
Tools and files w 18
0
Steps w 15
0
Result and completion w 14
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../seo/ecommerce-seo/WORKFLOW.md

Process rating: all ten parameters 26/100

Will not run. References files that are not bundled: ../../seo/ecommerce-seo/WORKFLOW.md
  • 0Tools and files. 1 referenced file(s) missing: ../../seo/ecommerce-seo/WORKFLOW.md
  • 0Steps. Prose only: no discrete steps
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 70When it triggers. States when to use, but not when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 62 tokens
  • 100Running it twice. No mutating operations

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)
  • +3Description length 924: 120–800 characters recommended
  • +4Structure: 1 headings, hard to scan
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -15SKILL.md body under 300 characters: nearly empty
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 12 example trigger phrases

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