product

Use when auditing e-commerce product pages or implementing structured data for a shop. Applies to any page selling or describing a specific product.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/product/SKILL.md

Quality

Content

65%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.

The body is a well-organized, concise overview that correctly delegates detail to a single real reference file. Its weaknesses are the absence of an inline executable JSON-LD example and an implicit rather than explicit validation feedback loop.

Suggestions

Include a minimal copy-paste-ready Product JSON-LD block in the body so the skill is actionable without opening the reference.

Reframe validation as an explicit feedback loop: validate with the Rich Results Test -> fix errors -> re-validate until passing.

De-duplicate the rich-results rationale between the intro paragraph and the '## Explain' section to reclaim tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with organized sections, but the rich-results rationale is restated between the intro paragraph and the '## Explain' section. Closest to 'efficient; minor instances of over-explanation that could be trimmed'; not a 5 due to that duplicated rationale, not a 3 because it is largely efficient.	4 / 5
Actionability	Lists concrete required/recommended fields and points to the Rich Results Test for validation, but the SKILL.md body contains no executable JSON-LD code block (code lives only in references/rule.md). Closest to 'some concrete guidance but incomplete; missing key details'; not a 4 because there is no copy-paste-ready example in the body itself, not a 2 because field-level guidance is specific.	3 / 5
Workflow Clarity	Check / Fix / Explain / Code Review sections provide a loose sequence and mention validation ('Validate with Google's Rich Results Test'), but there is no explicit numbered sequence or validate -> fix -> retry feedback loop. Closest to 'steps listed but validation gaps; checkpoints implicit'; not a 4 because the validation checkpoint is not framed as an explicit recovery loop, not a 2 because a rough sequence with validation is present.	3 / 5
Progressive Disclosure	Clear sectioned overview with a single, well-signaled, one-level-deep reference to references/rule.md (a real file), and content is appropriately split between the summary and the reference. Matches the 'clear overview with well-signaled one-level-deep references' anchor for a simple, under-50-line skill.	5 / 5
	Total	15 / 20 Passed

Description

70%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.

The description is well-structured with an explicit 'Use when' trigger and a clear e-commerce niche. It is concise and reasonably distinctive, though its 'what' is slightly abstract and it omits common synonyms like 'schema markup' and 'JSON-LD'.

Suggestions

Add concrete schema vocabulary to the 'what' clause, e.g. 'adding Product JSON-LD structured data' so the capability is unambiguous.

Include natural synonyms users say, such as 'schema markup', 'JSON-LD', and 'rich results', to broaden trigger coverage.

Tighten the 'when' clause with a few specific triggers like 'product detail pages', 'PDPs', or 'rich result eligibility'.

Dimension	Reasoning	Score
Specificity	Names the e-commerce domain and two concrete actions ('auditing e-commerce product pages', 'implementing structured data for a shop') but coverage is not comprehensive. Not a 4 because it does not enumerate several specific actions; not a 2 because it goes beyond naming the domain with minimal generic actions.	3 / 5
Completeness	Explicit 'Use when ...' trigger answers 'when' clearly, and 'auditing/implementing structured data' addresses 'what', though the 'what' is somewhat abstract (no explicit schema/JSON-LD wording). Not a 5 because 'what' lacks concrete trigger phrases; not a 3 because both what and when are present.	4 / 5
Trigger Term Quality	Includes natural terms like 'e-commerce product pages', 'structured data', 'shop', and 'page selling or describing a specific product', but misses common synonyms such as 'schema markup', 'JSON-LD', and 'rich results'. Closest to the 'good coverage, a few natural terms missing' anchor; not a 5 due to absent synonyms/extensions.	4 / 5
Distinctiveness Conflict Risk	Scoped to 'e-commerce product pages' and 'structured data for a shop', a fairly distinct niche with only minor overlap risk against broader SEO skills. Not a 5 because the domain is not razor-narrow; not a 3 because it is clearly more specific than generic SEO.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/product/SKILL.md
Commit: 30756a7

Reviewed: 18 days ago

Table of Contents

Discovery Implementation Validation

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.