schema-markup-generator

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/schema-markup-generator/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear validated workflow and well-structured one-level-deep references to real bundle files; its only weakness is redundant validation/checklist material that bloats token use.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but includes redundancy — the 'Validation Checkpoints' Input/Output checklists repeat the 'Validation Steps' and 'Validation Checklist' already given in the Instructions, and 'What This Skill Does' restates generic capability descriptions Claude already knows.	2 / 3
Actionability	It provides a complete, copy-paste-ready FAQPage JSON-LD example, concrete HTML implementation snippets, specific validator URLs (https://validator.schema.org/), and a schema-type quick-reference table — fully executable guidance.	3 / 3
Workflow Clarity	The three-step workflow (identify content type → generate schema → implement and validate) is clearly sequenced with explicit validation checkpoints, a validation checklist, and named external validators, matching the level-3 anchor.	3 / 3
Progressive Disclosure	Detailed material is split into real, clearly signaled one-level-deep references (schema-templates.md, schema-decision-tree.md, validation-guide.md, all present in references/), keeping SKILL.md an overview with easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

72%

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 concrete and distinctive with good trigger-term coverage, but it omits an explicit 'Use when' trigger clause within the description itself, leaving the 'when to use' half only weakly addressed there.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when generating JSON-LD, Schema.org markup, or rich snippet markup for a page.' so completeness reaches level 3.

Add one or two more concrete action verbs beyond 'Generate' (e.g. 'validate', 'audit and improve existing schema') to broaden the specificity of capabilities.

Consider including 'schema markup' and 'rich snippets' verbatim in the description alongside 'rich results', since these are common natural phrasings users say.

Dimension	Reasoning	Score
Specificity	The description names the domain and specific schema targets ('FAQ, HowTo, Article, Product, LocalBusiness rich results') but relies on a single action verb ('Generate JSON-LD structured data'), so it is not a comprehensive list of distinct concrete actions like the level-3 anchor (extract/fill/merge).	2 / 3
Completeness	It clearly states what the skill does ('Generate JSON-LD structured data...') but the description itself contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2 (the when is only present in the separate when_to_use field).	2 / 3
Trigger Term Quality	It covers natural user terms — 'JSON-LD', 'structured data', 'rich results', the individual schema types — and even adds multilingual variants ('Schema标记/结构化数据'), giving good coverage of phrasings users would actually say.	3 / 3
Distinctiveness Conflict Risk	The JSON-LD / structured-data / rich-results niche with named schema types is clearly distinct from other skills and unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Path: .cursor/skills/schema-markup-generator/SKILL.md
Commit: 3b319ce

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.