CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

schema

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, 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

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 well structured as an overview with excellent progressive disclosure to a complete examples reference, and its tables and tool links are actionable. Its weaknesses are internal duplication of required-property information, generic advice Claude already knows, and an implied rather than explicit implementation workflow with integrated validation checkpoints.

Suggestions

Remove the 'Quick Reference' section (or the 'Common Schema Types' table) — both list the same required properties for Organization, Article, Product, FAQPage, and BreadcrumbList, halving that content would tighten conciseness.

Replace the section ordering with an explicit numbered workflow (assess page type → select schema type → implement JSON-LD → validate in Rich Results Test → deploy and monitor Search Console) so validation is an integrated checkpoint rather than a standalone section.

Trim 'Core Principles' to only non-obvious guidance (e.g., Google-specific eligibility rules) and cut truisms like 'Test before deploying' and 'Don't markup content that doesn't exist' that Claude already knows.

DimensionReasoningScore

Conciseness

The body is mostly terse tables and bullets, but the 'Quick Reference' section repeats the required properties already listed in the 'Common Schema Types' table ('Required: name, url' appears for Organization in both), and 'Core Principles' states guidance Claude already knows ('Don't markup content that doesn't exist,' 'Test before deploying'). This fits anchor 3 — mostly efficient but could be tightened — rather than anchor 4, where over-explanation is only minor.

3 / 5

Actionability

Concrete guidance dominates: required properties per type, specific validation tool URLs ('https://search.google.com/test/rich-results'), per-stack implementation approaches, and a testing checklist. It falls short of anchor 5 because the body's own code blocks are skeletal placeholders ('{ "@type": "..." }' and '// Complete markup') rather than complete examples — though the full executable examples are delegated to the clearly linked references/schema-examples.md.

4 / 5

Workflow Clarity

The sequence (assess → choose type → implement → validate → monitor) is only implied by section ordering, and the 'Validation and Testing' section appears before 'Implementation,' so checkpoints are implicit rather than integrated into a sequenced process. This matches anchor 3 — steps present but checkpoints missing or implicit — and not anchor 4, which requires a clear sequence with most checkpoints wired in.

3 / 5

Progressive Disclosure

The SKILL.md is a genuine overview, and the 398-line catalog of complete JSON-LD examples is appropriately externalized to references/schema-examples.md — a real, one-level-deep file clearly signaled by 'For complete JSON-LD examples: See [references/schema-examples.md](references/schema-examples.md).' The bundle structure matches anchor 5's clean overview-plus-external-reference split.

5 / 5

Total

15

/

20

Passed

Description

90%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 with excellent trigger-term coverage, explicit what/when clauses, and explicit boundary routing to related skills. The only weakness is that the stated actions ('add, fix, or optimize') are a generic verb family rather than distinct concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain and a verb family ('add, fix, or optimize schema markup and structured data on their site'), but these are three generic variations of one operation rather than the varied concrete actions of anchor 4 (e.g., generating JSON-LD, validating markup, fixing Search Console errors). It sits above anchor 2 because the domain is precisely named with multiple stated actions.

3 / 5

Completeness

Both what and when are explicit: what = 'add, fix, or optimize schema markup and structured data,' and when = two explicit trigger clauses ('Also use when the user mentions...' and 'Use this whenever someone wants their pages to show enhanced results in Google'). This matches the anchor 5 example structure exactly.

5 / 5

Trigger Term Quality

The description lists a comprehensive set of natural trigger phrases users would actually say: 'schema markup,' 'structured data,' 'JSON-LD,' 'rich snippets,' 'schema.org,' 'FAQ schema,' 'product schema,' 'breadcrumb schema,' 'Google rich results,' 'knowledge panel,' 'star ratings in search,' and 'add structured data.' This matches anchor 5's comprehensive synonym coverage; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

The niche (schema.org structured data for rich results) is distinct with unique triggers, and the description explicitly disambiguates adjacent skills ('For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.'), minimizing conflict risk. It is clearly above anchor 4, which still allows minor overlap without such explicit routing.

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

joshmanders/dotfiles

Path

claude/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.