structured-data

Use when auditing metadata, crawlability, structured data, or indexability related to Add structured data markup. Verify the rendered HTML and HTTP response rather than relying only on source files.

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/structured-data/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 clean, well-organized overview that correctly pushes implementation detail to a single one-level-deep reference. Its weakness is that the body itself offers only high-level guidance without an explicit validation checkpoint in the workflow.

Suggestions

Add one small inline JSON-LD snippet in the Fix section so the body is actionable without requiring the reference for the common case.

Turn 'Validate with Google Rich Results Test' into an explicit numbered checkpoint in the Check/Fix flow (e.g., 'After adding markup, validate with Google Rich Results Test before shipping').

De-duplicate the 'rich snippets' benefit across the opening line, Quick Reference, and Explain section to tighten token use.

Dimension	Reasoning	Score
Conciseness	The ~30-line overview is lean and well-sectioned, with only minor repetition of the 'rich snippets' benefit across the opening line, Quick Reference, and Explain section.	4 / 5
Actionability	Names concrete vocabularies and tools (Schema.org, JSON-LD, Microdata, RDFa, Google Rich Results Test) but defers all executable code to references/rule.md, leaving the body itself at high-level guidance.	3 / 5
Workflow Clarity	A Check→Fix→Explain→Code Review sequence is present, but validation checkpoints are only implicit ('Validate with Google Rich Results Test' is a mention rather than an integrated step).	3 / 5
Progressive Disclosure	Clear overview with a well-signaled, one-level-deep reference ('see references/rule.md', verified to exist) that holds the bulk of the implementation detail.	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 provides a clear 'Use when' trigger with natural SEO terms and a concrete verification action, but its 'what' is narrow and the awkward embedding of the rule name weakens clarity. It is solid but not exemplary.

Suggestions

Lead with the core action (e.g., 'Audits and adds Schema.org structured data (JSON-LD) for rich snippets') before the 'Use when' clause so the 'what' is concrete and primary.

Add high-signal synonyms users actually say — 'rich snippets', 'JSON-LD', 'Schema.org' — to broaden trigger coverage.

Reword 'related to Add structured data markup' to integrate the rule name naturally instead of leaving it as a pasted title fragment.

Dimension	Reasoning	Score
Specificity	Names the SEO structured-data domain and 1-2 concrete actions ('auditing metadata, crawlability, structured data, or indexability' and 'Verify the rendered HTML and HTTP response'), but coverage is not comprehensive enough for a 4.	3 / 5
Completeness	Has an explicit 'Use when...' trigger clause and a 'what' (verify rendered HTML and HTTP response), but the 'what' is narrow and the embedded rule name 'Add structured data markup' makes the framing slightly muddled.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('structured data', 'metadata', 'crawlability', 'indexability') with good coverage, though synonyms like 'rich snippets', 'JSON-LD', or 'Schema.org' are missing.	4 / 5
Distinctiveness Conflict Risk	The structured-data auditing niche is mostly distinct, but triggers like 'metadata' and 'crawlability' overlap with sibling SEO audit skills.	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/structured-data/SKILL.md
Commit: 30756a7

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