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

62%

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

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The SKILL.md body is a well-structured, concise overview that correctly offloads detail to a real, one-level-deep reference file. Its weaknesses are the absence of executable code in the body itself and missing explicit validation/feedback-loop checkpoints for a verification-oriented task.

Suggestions

Add an explicit validate -> fix -> re-validate feedback loop (e.g. 'run Google Rich Results Test, fix flagged JSON-LD, re-run') to the Check/Fix workflow.

Include one short inline JSON-LD example or a concrete verification command so the body is actionable without opening the reference.

Trim the 'Explain' section's restatement of what structured data is, which Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly efficient, but the 'Explain' section ('Explain how structured data helps search engines understand page content...') and the opening line restate concepts Claude already knows, so it is mostly efficient with some unnecessary explanation that could be tightened.	2 / 3
Actionability	Guidance is concrete in places ('Check for JSON-LD, Microdata, or RDFa markup', 'Validate with Google Rich Results Test') but the SKILL.md body contains no executable code or commands itself; the actual copy-paste examples live in the referenced file, fitting the 'some concrete guidance but incomplete' anchor.	2 / 3
Workflow Clarity	The Check/Fix/Explain/Code Review sections give a recognizable sequence, but there are no explicit validation checkpoints or feedback loops (e.g. validate markup -> fix -> re-validate) for this verification-heavy task, so the sequence is present but checkpoints are implicit.	2 / 3
Progressive Disclosure	The body is a concise overview with well-organized sections and a single, clearly signaled one-level-deep reference ('see references/rule.md') that I verified exists as a real file, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	9 / 12 Passed

Description

67%

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 and answers both what and when, but is hampered by awkward phrasing ('related to Add structured data markup') and a lack of multiple concrete actions or common user-facing trigger terms like 'JSON-LD' and 'Schema.org'.

Suggestions

Replace the awkward clause 'related to Add structured data markup' with a concrete action, e.g. 'audit and verify structured data markup (JSON-LD, Microdata, RDFa) for rich results'.

Add common user-facing trigger terms such as 'JSON-LD', 'Schema.org', and 'rich snippets' so the description matches what users naturally say.

List a couple of concrete capabilities (e.g. 'validate JSON-LD against Schema.org, flag missing/incorrect markup') to raise specificity.

Dimension	Reasoning	Score
Specificity	It names the domain ('auditing metadata, crawlability, structured data, or indexability') and one concrete action ('Verify the rendered HTML and HTTP response'), but does not list multiple specific concrete actions like extracting or adding markup, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It explicitly answers both what ('auditing metadata, crawlability, structured data, or indexability') and when via an explicit 'Use when' trigger, matching the top anchor for clear what-and-when with explicit triggers.	3 / 3
Trigger Term Quality	It includes relevant natural terms ('structured data', 'indexability', 'crawlability', 'metadata'), but omits common user variations such as 'JSON-LD', 'Schema.org', 'rich snippets', or 'rich results', fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The structured-data/SEO auditing niche is fairly specific, but the phrasing 'related to Add structured data markup' is awkward and the broad metadata/crawlability framing could overlap with sibling SEO skills, fitting the 'somewhat specific but could still overlap' anchor rather than a clearly distinct niche.	2 / 3
	Total	9 / 12 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: 48405aa

Reviewed: about 7 hours 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.