CtrlK
BlogDocsLog inGet started
Tessl Logo

schema-markup-generator

Generate JSON-LD structured data for FAQ, HowTo, Article, Product, LocalBusiness rich results. Schema标记/结构化数据

57

Quality

66%

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

Quality

Content

67%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 with concrete examples and good progressive disclosure via real reference files, but it would benefit from trimming duplicated checklists and generic tips. Tightening the redundancy would push conciseness and overall quality higher.

Suggestions

Consolidate the validation checklist that appears in both 'Instructions' step 3 and 'Validation Checkpoints' into a single authoritative section.

Remove the duplicated 'Use this when...' sentences at the top of 'When This Must Trigger' and delete obvious 'Tips for Success' advice.

Move the full FAQ example or the Schema Type Quick Reference table into a reference file to reduce inline bulk and overlap with schema-decision-tree.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient but is padded by duplicate validation checklists (Instructions step 3 and a standalone Validation Checkpoints section), a redundant 'When This Must Trigger' opening, and generic 'Tips for Success' advice Claude already knows.

3 / 5

Actionability

Provides a complete, copy-ready FAQ JSON-LD example, concrete HTML implementation snippets, and specific validation URLs, with only minor reliance on placeholder templates for inputs.

4 / 5

Workflow Clarity

A clear three-step sequence (identify → generate → implement/validate) is paired with input and output validation checklists, though the error-recovery feedback loop is implicit rather than spelled out.

4 / 5

Progressive Disclosure

SKILL.md serves as an overview with clearly signaled one-level-deep references to schema-templates.md, schema-decision-tree.md, and validation-guide.md (all real bundle files), but some content like the quick-reference table and full example overlaps with those references.

4 / 5

Total

15

/

20

Passed

Description

66%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 specific and reasonably rich in trigger terms with multilingual coverage, but it omits an explicit 'when to use' clause from the description field itself, capping completeness. Adding a 'Use when...' clause inline would lift it to a 4–5.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when generating JSON-LD, Schema.org markup, or rich snippets for a page.'

Add common natural synonyms such as 'rich snippets' and 'schema.org markup' to broaden trigger coverage.

Lead with the most frequent user phrasing ('schema markup', 'structured data') before the enumerated schema types.

DimensionReasoningScore

Specificity

The phrase 'Generate JSON-LD structured data for FAQ, HowTo, Article, Product, LocalBusiness rich results' names one concrete action applied across five specific schema types, giving strong concrete coverage with only minor gaps.

4 / 5

Completeness

The description field gives a clear 'what' but contains no 'Use when...' clause; the trigger guidance lives in the separate when_to_use field, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural terms 'JSON-LD structured data', 'rich results', and multilingual synonyms ('Schema标记/结构化数据'), but misses common variations like 'rich snippets' or 'schema.org markup'.

4 / 5

Distinctiveness Conflict Risk

The JSON-LD/schema-markup niche with explicit schema types is mostly distinct from sibling SEO skills, with only minor overlap risk against related structured-data tools.

4 / 5

Total

15

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
MODSetter/SurfSense
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.