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

64%

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

Quality

Content

72%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-structured, concise overview that defers detail to one real reference file — strong progressive disclosure and actionability. Its main weakness is workflow clarity: the sections describe modes rather than an explicit validate→fix→re-validate sequence.

Suggestions

Convert Check/Fix into an explicit numbered sequence with a feedback loop, e.g. '3. Run Rich Results Test; 4. If errors, fix markup and re-test until clean'.

Trim or move the '35% click-through' motivation line into references to keep the body purely instructional.

Cross-link the specific property table in references/rule.md from the Fix section so the required-property detail is one click away.

Dimension	Reasoning	Score
Conciseness	The body is lean with concise Quick Reference bullets and short Check/Fix sections that assume Claude's competence; the only minor padding is the '35% click-through' motivation line, which could be trimmed.	4 / 5
Actionability	Guidance is concrete and actionable — it names exact JSON-LD types, required properties (ratingValue, ratingCount/reviewCount, bestRating), and a specific verification tool (Google's Rich Results Test); full executable code is appropriately deferred to references/rule.md, which is acceptable for an instruction/audit skill.	4 / 5
Workflow Clarity	Check/Fix/Explain/Code Review read as modes rather than a strictly sequenced workflow, and while the Rich Results Test is a validation checkpoint, there is no explicit 'fix then re-test' feedback loop, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	The ~30-line body is well-organized into labeled sections and signals a single one-level-deep reference ('see references/rule.md') that exists and holds the code examples and property tables, giving clear easy navigation.	5 / 5
	Total	16 / 20 Passed

Description

56%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 strong, explicit trigger guidance and a clear niche, but it lacks a concrete statement of what the skill does — it reads as a trigger list rather than a capability statement. Stating the action (e.g. 'Add and validate Review/AggregateRating schema markup') would lift specificity and completeness.

Suggestions

Lead with a concrete capability verb, e.g. 'Add and validate Review and AggregateRating schema markup...', so the 'what' is explicit rather than implied by 'auditing'.

Add natural synonyms users say — 'star ratings', 'rich snippets', 'schema markup', 'JSON-LD' — to broaden trigger-term coverage from 4 to 5.

Tighten the two 'Use when' clauses into one to reduce redundancy and make the trigger scan faster.

Dimension	Reasoning	Score
Specificity	The description names the domain extensively ('product pages, local business pages, recipes, apps, books') but states no concrete actions beyond the generic 'auditing rich result eligibility'; it never says it adds or validates schema markup, so actions are minimal.	2 / 5
Completeness	The 'when' is explicit via two 'Use when' clauses, but the 'what' is only weakly implied — 'auditing' suggests inspection rather than the skill's actual purpose (adding Review schema markup), so the what is not clearly stated.	3 / 5
Trigger Term Quality	Good natural keyword coverage with 'product pages', 'recipes', 'apps', 'books', 'user reviews', 'e-commerce', and 'review sites'; a few common synonyms (e.g. 'star ratings', 'schema markup', 'rich snippets') are missing.	4 / 5
Distinctiveness Conflict Risk	The review/e-commerce niche with enumerated eligible page types is mostly distinct from sibling SEO skills, with only minor overlap risk against general structured-data or schema skills.	4 / 5
	Total	13 / 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/review/SKILL.md
Commit: 30756a7

Reviewed: 13 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.