CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-ecommerce

Analyze ecommerce SEO across product pages, product schema, Shopping visibility, marketplace signals, and keyword gaps. Use only for stores, catalogs, or product listings.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly operational skill body with copy-paste-ready commands, explicit validation gates, and well-signaled one-level references. The main weakness is conciseness: date-sensitive details and UCP sourcing caveats are woven into the main body rather than isolated, adding tokens that will go stale.

Suggestions

Move time-sensitive dates and version specifics (UCP spec versions, Content API sunset 2026-08-18, hasAdultConsideration addition date) into a dedicated 'Changelog / Deprecated' section or into the relevant reference file, keeping the body date-free where possible.

Trim the UCP narrative paragraph (I/O 2026 keynote attribution, 'not confirmed on a Google-owned source' caveats) and push that sourcing detail into references/ucp-universal-commerce-protocol.md, keeping only the audit command and key flags inline.

Consider moving the granular recommended-property and validation-rule lists for Product schema into a reference file (or delegating to seo-schema), keeping only the required-fields JSON template and the scoring table inline.

DimensionReasoningScore

Conciseness

Checklists, tables, and commands are terse and token-efficient, but time-sensitive specifics are scattered inline (UCP spec dates, 'added 2026-05-20', 'sunsets 2026-08-18', 'documented 2026-09-08') instead of being consolidated in a deprecated/old-patterns section, and the UCP paragraph carries dense sourcing caveats that could be tightened or moved to its reference file.

3 / 5

Actionability

Fully executable commands with complete paths and flags ('dataforseo_merchant.py search "<keyword>" --marketplace google', 'ucp_check.py <url> --probe-endpoints --json'), a complete JSON-LD template, quantified thresholds (under 60 characters, ISO 4217, >= 200 words), and a copy-paste output template covering the common cases.

5 / 5

Workflow Clarity

Numbered workflows in sections 1 and 4 are clearly sequenced, and the MANDATORY cost guardrail is an explicit three-state validation gate (approved / needs_approval / blocked) with after-call logging; the error-handling table adds feedback loops (retry with backoff, Google-only fallback) for recovery.

5 / 5

Progressive Disclosure

Both referenced files (references/marketplace-endpoints.md, references/ucp-universal-commerce-protocol.md) exist, are clearly signaled at point of use, and are one level deep, with operational checklists appropriately inline; however, the ~378-line body inlines detailed UCP background prose and granular schema property notes that belong in the reference files.

4 / 5

Total

17

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and restricts when to use it with concrete ecommerce triggers, in proper third-person style. Keyword coverage and action diversity have minor gaps ('Google Shopping'/'Amazon' phrasing, pricing/comparison capabilities) that keep it just below the top anchors.

DimensionReasoningScore

Specificity

'Analyze ecommerce SEO across product pages, product schema, Shopping visibility, marketplace signals, and keyword gaps' names the domain plus five concrete analysis targets, matching the several-specific-actions anchor; it falls short of 5 because it leans on the single generic verb 'Analyze... across' and omits capabilities the body covers (pricing intelligence, Amazon comparison).

4 / 5

Completeness

It explicitly answers 'what' (analyze ecommerce SEO across five named areas) and 'when' ('Use only for stores, catalogs, or product listings') with concrete trigger phrases, matching the anchor-5 pattern of the reference example; the when-clause is specific and restrictive, not vague, so it is not a 4.

5 / 5

Trigger Term Quality

Natural phrases like 'ecommerce SEO', 'product pages', 'product schema', 'Shopping visibility', 'keyword gaps', and 'stores, catalogs, or product listings' give good keyword coverage, but common variations users would say ('Google Shopping', 'online store', 'Amazon') are missing.

4 / 5

Distinctiveness Conflict Risk

'Use only for stores, catalogs, or product listings' carves out a clear ecommerce niche with distinct triggers, but sibling skills in the same plugin family (seo-schema, seo-content, seo-images) touch the same product-page surface, leaving minor overlap risk rather than the minimal risk of anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

AgriciDaniel/claude-seo

Path

skills/seo-ecommerce/SKILL.md

Reviewed

Table of Contents

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.