CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/product/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 lean, field-level actionable overview with excellent progressive disclosure into a single verified reference file. The main weakness is structural redundancy: the intro/Explain pair and the Check/Code Review pair overlap substantially and could each be merged.

Suggestions

Merge the Explain section into the intro paragraph (or vice versa) — both make the same rich-results/CTR argument, so one copy suffices.

Consolidate Check and Code Review into a single verification section; they duplicate the same field checks, price-match check, and Rich Results Test step.

Inline one minimal copy-paste Product JSON-LD example in the Fix section so the most common case is executable without opening the reference file.

DimensionReasoningScore

Conciseness

Each section is individually lean, but the body has two clear redundancies: the intro ('rich results have significantly higher click-through rates than standard blue links') is restated almost verbatim in Explain ('These rich results have higher visual prominence and click-through rates'), and Check and Code Review both cover finding @type 'Product' JSON-LD, verifying required fields, price-matching, and Rich Results Test validation.

3 / 5

Actionability

Concrete field-level guidance ('offers.price, offers.priceCurrency (ISO 4217 code), offers.availability (schema.org URL)', 'aggregateRating (ratingValue, reviewCount), brand, sku, gtin13/gtin8/mpn') plus a named validation tool. Not 5 because no executable JSON-LD example appears in the body itself — code is deferred to references/rule.md.

4 / 5

Workflow Clarity

The Check → Fix → validate flow is legible from section order and validation is present ('Validate with Google's Rich Results Test'), so the missing-validation cap does not apply. Not 5 because the sequence is implicit rather than explicit, with no failure-recovery loop (what to do when the Rich Results Test fails) in the body.

4 / 5

Progressive Disclosure

A short, well-sectioned overview that defers full details via a clearly signaled, one-level-deep pointer: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — the file exists in the bundle and itself contains no further nested skill-file references.

5 / 5

Total

16

/

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.

A solid description with explicit trigger guidance and clear product-page scoping. Its weaknesses are the merged what/when phrasing — the actual capability (adding Product schema markup) is never stated — and missing central trigger synonyms like 'schema markup' and 'rich results'.

Suggestions

Lead with a capability statement naming the concrete deliverable, e.g. 'Adds Product JSON-LD schema markup (name, image, offers, aggregateRating) to e-commerce product pages for rich-result eligibility.'

Add the trigger synonyms users naturally say — 'product schema', 'schema markup', 'rich results', 'SEO' — to the 'Use when' clause.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions — 'auditing e-commerce product pages' and 'implementing structured data for a shop' — which matches the anchor for 1-2 concrete actions without comprehensive coverage. Not 4: only two actions are listed and the concrete deliverable (Product JSON-LD schema markup) is never named.

3 / 5

Completeness

An explicit 'Use when...' clause plus an applicability statement answer both what and when, satisfying the anchor for both-present-but-could-be-more-explicit. Not 5: the 'what' is embedded inside the trigger phrasing rather than stated as a distinct capability, and the concrete output (Product schema markup) is never mentioned.

4 / 5

Trigger Term Quality

Good natural-term coverage ('e-commerce product pages', 'shop', 'any page selling or describing a specific product', 'structured data'), going beyond the single-keyword anchor at 3. Not 5: common variations users would actually say — 'schema markup', 'SEO', 'rich results', 'JSON-LD' — are absent.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to product/shop pages ('Applies to any page selling or describing a specific product'), making it mostly distinct with only minor overlap risk. Not 5: 'implementing structured data for a shop' is broad enough to overlap with sibling SEO/structured-data skills (e.g., Organization or LocalBusiness schema).

4 / 5

Total

15

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/product/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.