CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

71%

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

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 tidy, reference-delegating overview with excellent progressive disclosure and good token efficiency. Its weakness is actionability: the Check and Fix sections name the right concepts but provide no executable commands or inline example, and the validation step floats outside the workflow rather than acting as a checkpoint after fixes.

Suggestions

Make the Check section executable: inline the basic commands (e.g., fetch the rendered page and grep for 'application/ld+json') and the Google Rich Results Test URL.

Integrate validation as an explicit checkpoint in the Check → Fix flow (e.g., 'After adding markup, re-fetch the rendered page and run the Rich Results Test') instead of leaving it as a standalone Quick Reference bullet.

De-duplicate the rich-snippet benefit sentence, which currently appears in the intro, the first Quick Reference bullet, and the Explain section.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no padding of concepts Claude already knows, but the rich-snippet benefit is stated three times ('Structured data enables rich snippets... increasing click-through rates' in the intro, 'Structured data enables rich snippets in search results' as the first Quick Reference bullet, and again nearly verbatim in Explain). Not score 5 because of that triplicated sentence; not score 3 because there is no substantive over-explanation, only minor redundancy.

4 / 5

Actionability

Concrete artifacts are named ('JSON-LD, Microdata, or RDFa markup', 'Schema.org vocabulary', 'Validate with Google Rich Results Test', types like 'Article, Product, FAQ, HowTo, LocalBusiness') but nothing is executable: no fetch/grep command for checking rendered HTML, no validator URL, no inline JSON-LD example — key details are deferred entirely to references/rule.md. Not score 4 because a user cannot act on the Check/Fix steps without opening the reference; not score 2 because the guidance does specify concrete formats, types, and the validation tool.

3 / 5

Workflow Clarity

Check → Fix → Explain → Code Review provides a recognizable sequence for an audit/fix skill, and verification is mentioned ('Validate with Google Rich Results Test', 'describe how to verify the final page output'), but no explicit validate-after-fix checkpoint exists — the validator appears only as a Quick Reference bullet, not as a step in the flow. Not score 4 because validation checkpoints are named but not integrated into the sequence; not score 2 because the Check/Fix ordering is coherent and the Code Review section does call out flagging routes and verifying final output.

3 / 5

Progressive Disclosure

A short, cleanly sectioned overview that delegates implementation detail to a single well-signaled, one-level-deep pointer: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and references/rule.md exists and covers exactly those topics (Code Example, per-type schema sections, Next.js integration, Verification). Not score 4 because there are no organization gaps: the split is appropriate and navigation is trivial.

5 / 5

Total

15

/

20

Passed

Description

66%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 a strong, explicit trigger clause with good natural keywords and one concrete verification instruction. Its weaknesses are the never-explicitly-stated core capability (the fragment 'related to Add structured data markup' carries it), missing synonyms like JSON-LD/schema.org/rich snippets, and over-broad claims into metadata/crawlability/indexability territory that sibling SEO skills likely cover.

Suggestions

State the core capability explicitly in third person (e.g., 'Audits and adds Schema.org JSON-LD structured data markup to webpages, verifying the rendered HTML and HTTP response') instead of the fragment 'related to Add structured data markup'.

Add natural synonyms users would say — 'JSON-LD', 'schema.org', 'rich snippets', 'rich results' — to improve trigger coverage.

Narrow or drop the 'metadata', 'crawlability', and 'indexability' trigger terms to reduce overlap/conflict with sibling SEO skills that own those areas.

DimensionReasoningScore

Specificity

Names the domain ('auditing metadata, crawlability, structured data, or indexability') and one concrete action ('Verify the rendered HTML and HTTP response rather than relying only on source files'), but the skill's core capability — adding/fixing Schema.org markup — is only implied by the fragment 'related to Add structured data markup'. Not score 4 because no list of several specific actions is given; not score 2 because the verification instruction and audit framing are concrete.

3 / 5

Completeness

Both parts are present: an explicit 'Use when auditing metadata, crawlability, structured data, or indexability...' trigger clause and a concrete what ('Verify the rendered HTML and HTTP response'). Not score 5 because the primary 'what' (add/repair structured data markup) is never stated as a capability — it survives only inside the awkward fragment 'related to Add structured data markup'; not score 3 because both what and when are explicitly present, not merely implied.

4 / 5

Trigger Term Quality

Natural trigger phrases a user would say include 'auditing', 'metadata', 'crawlability', 'structured data', 'indexability', 'rendered HTML', and 'HTTP response' — good coverage, but common variations like 'JSON-LD', 'schema.org', and 'rich snippets/rich results' are missing. Not score 5 for those missing synonyms; not score 3 because coverage goes well beyond one or two generic keywords.

4 / 5

Distinctiveness Conflict Risk

The structured-data/SEO niche is fairly distinct, but the description also claims 'metadata', 'crawlability', and 'indexability' — areas that sibling SEO checklist skills (meta tags rule, crawlability rule) would naturally own, creating real overlap risk. Not score 4 because those broad claims span multiple neighboring skills' territory; not score 2 because the structured-data core and rendered-HTML verification anchor it to a specific niche.

3 / 5

Total

14

/

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/structured-data/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.