CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-schema

Detect, validate, or generate Schema.org JSON-LD for a supplied page or entity. Use only when structured data or rich-result markup is requested.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-schema/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 information-dense with genuinely valuable post-training knowledge (2025-2026 Google rich-result retirements, @graph validation nuances, adult-product requirements) and concrete templates, but it is weakened by dead bundle references, inlined content that duplicates its own reference files, and boilerplate JSON-LD templates Claude could generate unaided.

Suggestions

Remove or externalize the three inline JSON-LD templates (Organization, LocalBusiness, Article) — they restate standard schema structures Claude already knows and duplicate the referenced schema/templates.json.

Fix the dead references: '../seo/references/schema-types.md' and 'schema/templates.json' do not exist in the bundle — either ship those files or replace the pointers with inline content, and trim the inline ACTIVE list to a few exemplars plus the pointer.

Make "Validate output before presenting" concrete: specify the validation checks or command to run and the fix-and-retry loop when validation fails.

DimensionReasoningScore

Conciseness

The core is dense, non-redundant post-training knowledge (2025-2026 retirement dates, @graph inheritance rules) that Claude cannot know, and most time-sensitive dates sit in the deprecation/status sections. However, ~70 lines of standard JSON-LD templates (Organization, LocalBusiness, Article) restate schema structures Claude already knows, and the full ACTIVE list re-inlines what "Read ../seo/references/schema-types.md for the full list" points to — more than minor trimming, so anchor 3 rather than 4.

3 / 5

Actionability

Concrete and mostly executable: a specific detection command ("${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo run parse_html.py --url <url> --json"), copy-paste-ready templates with explicitly justified placeholders, a scenario→action error table, and named output files (SCHEMA-REPORT.md, generated-schema.json). Not 5 because the primary parse command depends on a script absent from the bundle, and "Validate output before presenting" names no mechanism.

4 / 5

Workflow Clarity

Detection, Validation, and Generation are clearly sequenced, with a validation checkpoint ("Validate output before presenting") and an Error Handling table mapping failures to recovery actions (e.g., invalid JSON-LD → parse, report, provide corrected output). Not 5 because the generation-time validation step lacks an explicit method or fix-and-retry loop — it says to validate but not how or what to do on failure.

4 / 5

Progressive Disclosure

Sections are well organized and references/deprecated-types-2024-2026.md is a valid, clearly signaled one-level-deep pointer, but two other referenced paths — "../seo/references/schema-types.md" and "schema/templates.json" — do not exist in the bundle, and the inline ACTIVE list and templates duplicate what those files should hold. Anchor 3: structure is present but navigation is undermined by dead references and content that belongs in the referenced files.

3 / 5

Total

14

/

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: a concrete three-verb capability statement, an explicit and appropriately restrictive trigger clause, and a well-defined niche that is unlikely to fire for the wrong skill. Only minor headroom exists in keyword synonyms (e.g., "rich snippets", "schema markup") and breadth of mentioned capabilities.

DimensionReasoningScore

Specificity

"Detect, validate, or generate Schema.org JSON-LD" names the domain and three concrete actions with a clear target ("for a supplied page or entity"), but coverage has minor gaps — no mention of Microdata/RDFa detection or the report/output artifacts the skill produces. Matches the anchor "lists several specific actions; minor gaps in coverage" rather than 5's comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ("Detect, validate, or generate Schema.org JSON-LD for a supplied page or entity") and when ("Use only when structured data or rich-result markup is requested") with concrete trigger conditions. The 'when' clause is explicit and restrictive, so this matches anchor 5 rather than 4's "when could be more explicit".

5 / 5

Trigger Term Quality

Natural trigger phrases are present — "structured data", "rich-result markup", "Schema.org JSON-LD" — but common user synonyms such as "rich snippets", "schema markup", or "SEO" are missing. Good keyword coverage with a few natural terms missing fits anchor 4, not 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (structured data / rich-result markup) with a restrictive "Use only when" trigger that minimizes overlap with general SEO or web-analysis skills. Matches anchor 5's "clear niche with distinct triggers; minimal conflict risk".

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

AgriciDaniel/claude-seo

Path

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