CtrlK
BlogDocsLog inGet started
Tessl Logo

schema-markup-generator

Use when the user asks to "add schema markup", "generate structured data", "JSON-LD", "rich snippets", "FAQ schema", "add FAQ rich results", "I want star ratings in Google", "product markup", or "recipe schema". Generates structured data markup (Schema.org JSON-LD) to enable rich results in search engines including FAQ snippets, How-To cards, Product listings, Reviews, and more. For meta tag optimization, see meta-tags-optimizer. For broader technical SEO, see technical-seo-checker.

64

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 ./.agents/skills/schema-markup-generator/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 skill body is highly actionable — complete templates, validation tools, checklists, and a worked example — but it is severely over-inflated relative to its own reference files: ~785 lines that largely duplicate references/schema-templates.md, with four overlapping tables and a promotional nav block. Corrupted "~~" placeholders and broken relative links further degrade workflow and navigation quality.

Suggestions

Remove the eight full inline JSON-LD template blocks from SKILL.md and replace them with brief per-type summaries that point to ./references/schema-templates.md, which already contains the same templates.

Consolidate the four overlapping tables (Schema Type Quick Reference, Decision Tree, Industry-Specific Recommendations, Implementation Priority) into one compact mapping table, moving the rest into a reference file.

Fix the corrupted "~~" placeholders ("~~schema validator", "~~search console", "~~web crawler") with the real tool names, and repair or remove the broken relative links ../../CONNECTORS.md and ../../references/core-eeat-benchmark.md.

DimensionReasoningScore

Conciseness

The ~785-line body inlines complete JSON-LD templates for 8 schema types that substantially duplicate references/schema-templates.md, plus a library cross-promotion nav block and four overlapping tables (Quick Reference, Decision Tree, Industry-Specific, Implementation Priority). This is noticeably verbose with several padded/duplicated sections rather than only minor over-explanation, fitting the 2 anchor.

2 / 5

Actionability

Complete copy-ready JSON-LD templates with bracketed values, concrete validation URLs (validator.schema.org, rich results test), HTML implementation placement options, and a fully worked executable FAQPage example cover the common cases end to end, matching the 5 anchor.

5 / 5

Workflow Clarity

The 10-step sequence (identify content type → map schema → generate → implement/validate) is clear with explicit Input/Output validation checklists, but there is no error-recovery loop after validation failures and the validator names are corrupted placeholders ("~~schema validator", "~~search console"), so it falls short of the 5 anchor.

4 / 5

Progressive Disclosure

References are one level deep and clearly signaled in a "Reference Materials" section, but the template content that belongs in those files is duplicated inline in SKILL.md, and two referenced paths (../../CONNECTORS.md, ../../references/core-eeat-benchmark.md) do not resolve from this bundle — "content that should be separate is inline" matches the 3 anchor.

3 / 5

Total

14

/

20

Passed

Description

95%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.

The description is a near-exemplar: it explicitly answers both what the skill does and when to use it, with a rich set of natural trigger phrases users would actually say, in third person. Its only minor weakness is that a single verb ("generates") carries the capability statement rather than enumerating several distinct actions.

DimensionReasoningScore

Specificity

"Generates structured data markup (Schema.org JSON-LD) to enable rich results in search engines including FAQ snippets, How-To cards, Product listings, Reviews, and more" names the domain and concrete output types in third person, but a single verb ("generates") carries all actions, so it lists several specifics without the multi-action comprehensiveness of a 5.

4 / 5

Completeness

An explicit "Use when the user asks to…" clause with concrete quoted trigger phrases answers "when", and "Generates structured data markup (Schema.org JSON-LD) to enable rich results…" clearly answers "what" — both present and explicit, matching the 5 anchor.

5 / 5

Trigger Term Quality

"add schema markup", "generate structured data", "JSON-LD", "rich snippets", "FAQ schema", "add FAQ rich results", "I want star ratings in Google", "product markup", "recipe schema" — comprehensive natural-term coverage including colloquial phrasings users would actually say, matching the top anchor exactly.

5 / 5

Distinctiveness Conflict Risk

The schema-markup/JSON-LD niche is distinct, and the description actively disambiguates its nearest neighbors ("For meta tag optimization, see meta-tags-optimizer. For broader technical SEO, see technical-seo-checker."), keeping conflict risk minimal.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (787 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 27 suspicious

Warning

Total

13

/

16

Passed

Repository
teeclaw/phorm-nft
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.