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 dense, highly actionable reference with executable commands, explicit cost-validation checkpoints, and clear per-section workflows. Its main weakness is token efficiency: the UCP section and scattered time-sensitive dates inline detail that belongs in reference files or a deprecation section.

Suggestions

Move the UCP market-partner, versioning, and rollout-history detail (payment partners, I/O keynote coverage, 2026-08-25 vs 2026-04-08 spec dates) into references/ucp-universal-commerce-protocol.md, keeping only the audit command and the version-format rule inline.

Consolidate the time-sensitive dates scattered across the schema and cross-skill sections (hasAdultConsideration added 2026-05-20, Content API sunset 2026-08-18, EEA unit changes 2026-09-08/18) into a single 'Recent changes / deprecations' subsection so they don't bloat the operative checklists.

Trim the cross-skill integration table's long parentheticals to one-line integration points, linking to the sibling skill's reference for regional-eligibility rules.

DimensionReasoningScore

Conciseness

Checklists, command blocks, and tables are lean, but the UCP section inlines ~25 lines of partner lists and versioning history duplicating references/ucp-universal-commerce-protocol.md, and numerous time-sensitive dates (2026-05-20, 2026-08-18, 2026-08-25, 2026-09-08/18) sit inline outside any deprecated/old-patterns section.

3 / 5

Actionability

Fully executable copy-paste bash commands with complete "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" invocations, a concrete JSON-LD example, mandatory cost-check/log commands with defined statuses, and an error-response table covering the common cases.

5 / 5

Workflow Clarity

Each section has an explicit numbered or labeled sequence, a mandatory pre-call validation checkpoint (cost check with approved/needs_approval/blocked outcomes) plus post-call logging, and an error-handling table providing feedback loops (retry with backoff, fall back to Google-only, non-product page rerouting).

5 / 5

Progressive Disclosure

Both referenced files (references/marketplace-endpoints.md, references/ucp-universal-commerce-protocol.md) exist and are clearly signaled one level deep, but the UCP section inlines detail that belongs in its reference file, and marketplace-endpoints.md points onward to a sibling skill's cost-tiers.md.

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: concrete scope, explicit third-person use-when triggers, and a well-delineated e-commerce niche. Its only gaps are single-verb phrasing of capabilities and a few missing natural trigger synonyms.

DimensionReasoningScore

Specificity

"Analyze ecommerce SEO across product pages, product schema, Shopping visibility, marketplace signals, and keyword gaps" names several specific analysis targets, but leans on a single verb ('Analyze...across') rather than multiple distinct concrete actions, so it matches anchor 4 with minor coverage gaps rather than the comprehensive multi-action anchor 5.

4 / 5

Completeness

It explicitly answers both 'what' (analyze ecommerce SEO across five named areas) and 'when' with concrete trigger phrases ("Use only for stores, catalogs, or product listings"), matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

"ecommerce SEO", "product pages", "product schema", "Shopping visibility", "stores, catalogs, or product listings" are natural user phrases with good coverage, but common variations like 'online store', the phrase 'Google Shopping', and 'Amazon' are missing, fitting anchor 4 rather than the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The 'Use only for stores, catalogs, or product listings' scoping carves a clear niche, but 'product schema' overlaps the sibling seo-schema skill and Shopping/marketplace data overlaps seo-dataforseo, so it is mostly distinct with minor overlap risk rather than minimal conflict.

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.