CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

geo-schema

Schema.org structured data audit and generation optimized for AI discoverability — detect, validate, and generate JSON-LD markup

Quality

72%

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

A thorough, well-sequenced audit workflow with strong concrete artifacts (scoring rubric, output template, generation rules), undermined by a monolithic structure that inlines schema.org boilerplate Claude already knows and references a fetch script that is missing from the bundle. Tightening it means moving per-type property lists to reference files and fixing or removing the fetch_page.py dependency.

Suggestions

Move the per-type property lists (Step 3) into references/ files (e.g., references/organization.md, references/article.md, references/product.md) and keep one-line summaries with links in SKILL.md, cutting the body roughly in half.

Either bundle scripts/fetch_page.py or replace the instruction with an inline executable approach (e.g., a curl + python json-ld extraction snippet) so the detection step is not a broken reference.

Add an explicit validate → fix → re-validate loop after Step 2 (e.g., 'if a schema fails validation, regenerate it with the missing properties before scoring') to close the workflow's feedback gap.

DimensionReasoningScore

Conciseness

Steps 3 and 6 spend ~180 lines enumerating standard schema.org required/recommended properties (Article needs headline/datePublished/author, PostalAddress fields, a full Organization JSON template, a WebSite+SearchAction block) that Claude already knows, matching 'mostly efficient but includes some unnecessary explanation or could be tightened'. Not 2 because the GEO-specific annotations (knowsAbout as a strong signal, sameAs priority order, Dec 2025 JS-injection guidance, deprecation table) are genuinely non-obvious and earn their tokens; not 4 because the boilerplate property lists and templates are a large share of the document.

3 / 5

Actionability

Concrete commands ("python3 ~/.claude/skills/geo/scripts/fetch_page.py <url> page"), a copy-paste Organization JSON-LD template, a 0-100 scoring rubric with per-criterion point rules, and a full output-format skeleton make the guidance mostly executable. Not 5 because the only command is a script that is not in the bundle (no scripts/ directory exists), and generation guidance for types other than Organization is property-list-only with no complete examples.

4 / 5

Workflow Clarity

A clear 6-step sequence (detect → validate → identify gaps → generate → report) with a numbered "How to Use" summary and an 8-point validation checklist in Step 2; the scoring rubric and output template define explicit completion criteria. Not 5 because there is no explicit feedback loop (e.g., 'if validation fails, fix the JSON-LD and re-check before generating the report') — checkpoints are listed but recovery steps are implicit.

4 / 5

Progressive Disclosure

Section structure is clear and well-ordered, but everything is inlined in a single ~370-line file: the per-type property references in Step 3 are exactly the content that belongs in separate reference files, and the sole external reference (fetch_page.py) points to a path that does not exist in the bundle (no scripts/ directory), so it doesn't resolve. This matches 'some structure but... content that should be separate is inline' rather than 2, since headers and navigation are good, and not 4 because the one bundle reference is broken and no reference files exist at all.

3 / 5

Total

14

/

20

Passed

Description

70%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 specific, third-person description that clearly states what the skill does with concrete verbs and strong domain keywords. Its main weakness is the complete absence of trigger guidance ('use when...'), which both caps completeness and leaves the description relying solely on keyword matching for activation.

Suggestions

Add an explicit trigger clause, e.g. "Use when auditing a site's schema markup, adding JSON-LD structured data, or improving AI/LLM search visibility (GEO)."

Include common synonyms users say — "schema markup", "rich results", "structured data", "microdata" — so the description matches natural phrasings beyond "JSON-LD".

Optionally mention the deliverable (emits a GEO-SCHEMA-REPORT.md with a 0-100 score) to sharpen the what.

DimensionReasoningScore

Specificity

"detect, validate, and generate JSON-LD markup" lists several concrete actions (audit, detect, validate, generate) in the schema.org domain, matching the 'lists several specific actions; minor gaps in coverage' anchor. Not 5 because coverage is compressed — the body's actual scope (multi-format detection, scoring, report generation) isn't reflected, and not 3 because more than 1-2 concrete actions are named.

4 / 5

Completeness

The "what" is clear (audit and generation of schema.org/JSON-LD markup for AI discoverability), but there is no "Use when..." clause or any trigger guidance — the "when" is entirely absent, which per the judging guidelines caps completeness at 3. Not 4 because 'when' is not even weakly implied by the text itself.

3 / 5

Trigger Term Quality

"Schema.org structured data", "JSON-LD", and "AI discoverability" are natural terms users would say when needing this skill, giving good keyword coverage. Not 5 because common synonyms and variations are missing ("schema markup", "rich results", "microdata", "SEO"); not 3 because the included keywords are the primary natural phrasings, not just generic ones.

4 / 5

Distinctiveness Conflict Risk

"Schema.org structured data", "JSON-LD", and "AI discoverability" define a clear niche with distinct triggers that would not naturally fire for other skills. There is minor conceivable overlap with a generic SEO-audit skill, but the entity/structured-data focus keeps conflict risk minimal — matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

zubair-trabzada/geo-seo-claude

Path

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