CtrlK
BlogDocsLog inGet started
Tessl Logo

schema-markup

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," or "breadcrumb schema." For broader SEO issues, see seo-audit.

65

Quality

78%

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 ./config/claude/skills/schema-markup/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is a well-structured overview with good progressive disclosure, but it loses tokens to redundant property listings and offers templated rather than executable code examples. Tightening duplication and adding a concrete validate-fix-retry loop would lift it.

Suggestions

Merge the Common Schema Types table and the Quick Reference section into a single source of required/recommended properties to remove the duplication.

Replace the placeholder Output Format example ("// Complete markup") with one complete, copy-paste-ready JSON-LD block for a representative page type.

Add an explicit numbered validation workflow: implement → run Rich Results Test → if errors, fix and re-test → deploy only when clean.

DimensionReasoningScore

Conciseness

Mostly efficient reference tables, but the Common Schema Types table and the Quick Reference section repeat the same required properties, and Task-Specific Questions restates the Initial Assessment prompts.

2 / 3

Actionability

Concrete property lists and validation tool URLs are useful, but the Output Format example is templated ("// Complete markup") and the @graph example uses "..." placeholders rather than copy-paste-ready code.

2 / 3

Workflow Clarity

A sequence is implied (assess → implement → test) with a testing checklist, but there is no explicit validate→fix→retry feedback loop sequenced as steps.

2 / 3

Progressive Disclosure

Well-organized sections with a single clearly-signaled one-level reference to references/schema-examples.md (verified to exist), matching the top anchor.

3 / 3

Total

9

/

12

Passed

Description

100%

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 is exemplary: it names concrete actions, lists natural trigger terms, answers both what and when with an explicit use-when clause, and distinguishes itself from sibling SEO skills. No changes needed.

DimensionReasoningScore

Specificity

"add, fix, or optimize schema markup and structured data on their site" lists multiple specific concrete actions matching the highest anchor.

3 / 3

Completeness

Explicitly states what it does (add/fix/optimize schema markup) and when to use it via an explicit "Also use when the user mentions..." trigger clause, satisfying both halves.

3 / 3

Trigger Term Quality

Covers a strong set of natural terms users would say: "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," plus FAQ/product/review/breadcrumb schema.

3 / 3

Distinctiveness Conflict Risk

Clear niche with distinct triggers, and it actively disambiguates by deferring broader SEO concerns to seo-audit, reducing conflict risk.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
freekmurze/dotfiles
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.