CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review

Use when applies to product pages, local business pages, recipes, apps, books, and any page that aggregates user reviews. Use when auditing rich result eligibility for e-commerce or review sites.

Quality

69%

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/review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-structured overview: concrete check/fix guidance with exact schema strings and properties, an explicit validation tool, and clean one-level-deep progressive disclosure into references/rule.md. Its only weaknesses are minor — a duplicated property list across two sections, a padded motivational opener, and no inline JSON-LD example in the Fix section.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and assumes Claude's competence (no explanation of what JSON-LD or schema.org is), but the required-properties list ('ratingValue', 'ratingCount'/'reviewCount', 'bestRating') is repeated nearly verbatim in both 'Quick Reference' and 'Check', and the CTR-justification opener ('competitors with valid markup capture that visibility advantage') is padding that could be trimmed. This matches anchor 4 (efficient with minor instances of over-explanation) rather than 5 (every token earns its place).

4 / 5

Actionability

Concrete, executable guidance throughout: exact search strings ('"@type": "Review"' / '"@type": "AggregateRating"'), exact required properties, where to nest AggregateRating ('inside the main entity (Product, LocalBusiness, etc.)'), and the named validation tool (Google's Rich Results Test). It stops short of an inline JSON-LD snippet in 'Fix' — full code lives one level deeper in references/rule.md — leaving a minor gap consistent with anchor 4 rather than the copy-paste-ready completeness of 5, and well above anchor 3 since nothing is pseudocode or missing key details.

4 / 5

Workflow Clarity

A clear implied Check -> Fix -> Validate sequence with the validation tool named twice ('Validate markup with Google's Rich Results Test before deploying'). However, there is no explicit error-recovery loop (what to do when the test reports errors) and no post-deploy re-crawl step in the body itself, matching anchor 4 (clear sequence, most checkpoints present) rather than 5 (explicit validation steps with feedback loops); not 3, since validation checkpoints are explicitly present rather than missing.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview that defers all implementation details, code examples, and framework-specific guidance to a single clearly signaled reference ('see references/rule.md'), which exists in the bundle and is exactly one level deep with no nested references. This matches anchor 5 (clear overview with well-signaled one-level-deep references, content appropriately split).

5 / 5

Total

17

/

20

Passed

Description

47%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 has good trigger-term coverage and a reasonably distinct SEO niche, but it omits any statement of what the skill does and opens with broken grammar ('Use when applies to'), leaving it a pure trigger list rather than a capability description. Adding a concrete 'what' clause and natural synonyms like 'star ratings' would lift it substantially.

Suggestions

Add a third-person 'what' clause before the triggers, e.g. 'Adds and validates Review / AggregateRating JSON-LD schema markup so pages earn star-rating rich results. Use when...' — this fixes both the missing 'what' (completeness) and the broken 'Use when applies to' opener (specificity).

Include concrete actions in the 'what' clause: add JSON-LD with AggregateRating nested inside the main entity, verify required properties (ratingValue, reviewCount, bestRating), and validate with Google's Rich Results Test.

Add natural trigger synonyms users would actually say: 'star ratings', 'rich results', 'rich snippet', 'review schema', 'structured data' — currently the central terms for this domain are missing.

DimensionReasoningScore

Specificity

The description names concrete domains ('product pages, local business pages, recipes, apps, books, and any page that aggregates user reviews') but contains no concrete actions — its only verb is the generic 'auditing' ('Use when auditing rich result eligibility'). It matches anchor 2 (names the domain, actions minimal or generic) rather than anchor 3, which requires 1-2 concrete actions such as 'adds Review/AggregateRating JSON-LD markup'; it is above anchor 1 because the page types are concrete, not pure abstraction.

2 / 5

Completeness

Only the 'when' is present (two 'Use when...' clauses with concrete page types); the 'what' is entirely absent — nothing states what the skill does. This matches anchor 2 ('only when is present without what', as in 'Use when working with documents'), and the garbled opener 'Use when applies to' further weakens trigger clarity; not 1, because the 'when' clause is explicit and reasonably specific.

2 / 5

Trigger Term Quality

Good natural keyword coverage: 'product pages', 'local business pages', 'recipes', 'apps', 'books', 'user reviews', 'e-commerce', 'review sites', 'rich result eligibility'. Central synonyms a user would naturally say — 'star ratings', 'rich results', 'rich snippet', 'review schema', 'structured data' — are missing, placing it at anchor 4 (good coverage, a few natural terms missing) rather than the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to review/rating-bearing pages and rich-result eligibility audits, which is a clear niche with mostly distinct triggers. However, 'product pages', 'recipes', and 'apps' would equally match sibling SEO skills (e.g. Product or Recipe schema-markup rules in the same frontendchecklist family), giving minor overlap risk — anchor 4 (mostly distinct) rather than 5 (minimal conflict risk).

4 / 5

Total

12

/

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/review/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.