CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

json-ld-valid

Use when generating or auditing any `<script type='application/ld+json'>` blocks, implementing structured data for articles, products, FAQs, breadcrumbs, or local businesses, or investigating why rich results are not appearing in Google Search Console.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-structured, actionable skill body with clear sequenced workflows, explicit validation steps, and exemplary progressive disclosure to a verified one-level-deep reference. Its main weakness is redundancy: the silent-ignore fact and the validation steps are each repeated across two or three sections, and the Code Review section largely duplicates Check.

Suggestions

Remove the duplication of the silent-ignore fact: it appears in the intro, Quick Reference, and Explain — state it once (ideally in the intro) and cut the rest.

Merge or cut the Code Review section, which restates the Check steps (parse, verify @context, check @type, validate required properties) almost verbatim.

Tighten the Explain section: what rich results are and that Google uses structured data are concepts Claude already knows; keep only the non-obvious insight (validation failures are only discoverable via the Rich Results Test).

DimensionReasoningScore

Conciseness

The bulk (Check, Fix) is efficient and actionable, but the silent-ignore fact is stated three times (intro, "Invalid JSON (unclosed brackets, missing commas) causes the entire block to be silently ignored", and the Explain section), and the Code Review section restates the Check steps almost verbatim. This fits "mostly efficient but includes some unnecessary explanation or could be tightened" rather than anchor 2, since there is no concept-explanation padding and over half the body is tight actionable content.

3 / 5

Actionability

Concrete, executable guidance throughout: "Parse the JSON-LD with JSON.parse()", the exact "https://schema.org" value, enumerated required properties per type (Article: headline, author, datePublished; Product: name; FAQPage: mainEntity; BreadcrumbList: itemListElement), and two validation URLs. Minor gaps keep it below anchor 5: no inline code examples (delegated to the reference, acceptable for an instruction-only skill) and "Run through Google's Rich Results Test API if available" lacks an endpoint or command.

4 / 5

Workflow Clarity

Check (5 numbered steps) and Fix (6 numbered steps) are clearly sequenced, each terminating in explicit validation steps (Rich Results Test, jsonlint). It falls short of anchor 5 because no explicit feedback loop ("if validation fails, fix and re-validate") connects the sections, though this is a non-destructive single-page task so no cap applies.

4 / 5

Progressive Disclosure

The body is under 50 lines, cleanly sectioned (Quick Reference, Check, Fix, Explain, Code Review), and closes with a clearly signaled one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — which exists as a real 160-line file with code examples. The split is appropriate: overview and core workflow inline, full examples in the reference.

5 / 5

Total

16

/

20

Passed

Description

87%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.

A strong, highly targeted trigger-style description that names concrete actions, natural domain keywords, and three explicit trigger scenarios with minimal conflict risk. Its only weaknesses are unnamed validation/fix actions and missing synonyms like "schema markup" or "schema.org".

DimensionReasoningScore

Specificity

The description lists several concrete actions — "generating or auditing", "implementing structured data", "investigating why rich results are not appearing" — across the domain's entity types, but the skill's core validating/fixing actions are never named, leaving minor gaps in coverage. It is well above anchor 3 (only 1-2 concrete actions) but short of anchor 5's comprehensive coverage.

4 / 5

Completeness

Both elements are explicit: an explicit "Use when..." clause with three concrete trigger scenarios answers "when", and the action verbs (generate, audit, implement, investigate) explicitly answer "what". The "when" is more specific than the anchor 4 example (whose weakness is a vague "when"), matching anchor 5's requirement of concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keywords users would say in this context: "JSON-LD", "structured data", "rich results", "Google Search Console", plus entity types (articles, products, FAQs, breadcrumbs, local businesses). Common synonyms like "schema markup" or "schema.org" are missing, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: the literal `<script type='application/ld+json'>` tag, JSON-LD, rich results, and Google Search Console would only match structured-data work, creating minimal conflict risk with any other skill.

5 / 5

Total

18

/

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/json-ld-valid/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.