CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

schema

When the user wants to add, fix, or validate schema markup (JSON-LD), or asks which type fits a page or whether some markup is allowed: product, review, recipe, FAQ, rich result eligibility (FAQ no longer earns Google rich results), Search Console errors. For broader SEO, see seo-audit. For AI search, see ai-seo.

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

67%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, actionable reference: accurate type tables, current feature-support warnings with sources, concrete validator links, and a verified one-level-deep examples reference. Its main weaknesses are redundancy — type/property listings appear twice and the FAQ-retirement caveat is repeated — and the lack of an explicit error-recovery loop in the validation workflow.

Suggestions

Consolidate the duplicated type/required-property listings: either drop the Quick Reference section or fold it into the Common Schema Types table (or into references/schema-examples.md) so each fact appears once.

State the FAQ/HowTo/sitelinks retirement caveat once in the feature-support section and reference it from the FAQPage entry instead of repeating it, and trim overly precise date details (e.g., "removed the feature's documentation in June").

Add an explicit validation feedback loop, e.g. after the Testing Checklist: if the Rich Results Test or Schema.org Validator reports errors, fix the flagged properties and re-run the test before delivering the markup.

DimensionReasoningScore

Conciseness

Mostly terse tables and bullets with no padding about concepts Claude already knows, but the "Common Schema Types" table and the "Quick Reference" section duplicate required-property listings for Organization/Article/Product/FAQPage/BreadcrumbList, and the FAQ-retirement caveat is stated in both "Check Google Feature Support First" ("Google stopped showing FAQ rich results on May 7, 2026") and the FAQPage entry ("not a way to obtain Google FAQ rich results"). This matches anchor 3: mostly efficient but could be tightened.

3 / 5

Actionability

Provides concrete guidance: required-property tables, specific validator URLs (Rich Results Test, validator.schema.org), per-stack implementation notes, and a @graph example. Minor gaps: the @graph and Output Format snippets use "..." placeholders rather than executable JSON (full examples are delegated to the reference file), fitting anchor 4 rather than the fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

A logical assess → select type → check feature support → implement → validate flow is conveyed through section order, the Initial Assessment questions, and an explicit Testing Checklist with checkpoints. No destructive or batch operations, so no validation cap applies; the gap keeping it below 5 is the absence of an explicit validate → fix → re-validate error-recovery loop ("Fix errors promptly" only hints at it).

4 / 5

Progressive Disclosure

A single, clearly signaled, one-level-deep reference exists and is real ("For complete JSON-LD examples: See [references/schema-examples.md]"), and the body works as an overview with quick-reference material. Minor organization gaps — the duplicated type/property tables could consolidate into the reference file — place it at anchor 4 rather than the cleanly split anchor 5.

4 / 5

Total

15

/

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 description: it states concrete capabilities in third person, opens with an explicit trigger clause, names the domain's key entities, and explicitly disambiguates from adjacent SEO skills. Its only notable gap is omitting the very common synonyms "structured data" and "schema.org" from its trigger vocabulary.

DimensionReasoningScore

Specificity

Lists several concrete actions — "add, fix, or validate schema markup (JSON-LD)", "which type fits a page", "whether some markup is allowed" — across named domains (product, review, recipe, FAQ, Search Console errors). Not a fully comprehensive capability enumeration (e.g., generating markup from page content is only implied), so it sits at anchor 4 rather than 5, but is clearly above the 1-2-action anchor 3.

4 / 5

Completeness

Explicitly answers both: what ("add, fix, or validate schema markup (JSON-LD)", type selection, eligibility checks) and when ("When the user wants to... or asks which type fits a page or whether some markup is allowed") with concrete trigger phrases, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Includes natural phrases users would say: "schema markup", "JSON-LD", "rich result", "Search Console errors", "FAQ", plus type names. However the most common user synonyms "structured data" and "schema.org" are missing, matching anchor 4 (good coverage, a few natural terms missing) rather than 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (JSON-LD/rich-result markup and validation) with explicit boundary-setting against sibling skills ("For broader SEO, see seo-audit. For AI search, see ai-seo."), giving minimal conflict risk and matching the anchor-5 clear-niche example.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/schema/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.