serp-markup-builder

Use when the user asks to "optimize meta tags", "write title tags / meta descriptions", "add Open Graph or Twitter cards", or "generate schema / JSON-LD" for FAQ, HowTo, Article, Product, or LocalBusiness rich-result candidates. Produces title/description options, an OG+Twitter block, and validated JSON-LD for the document head. Not for body copy — use content-writer; not for crawl/index technical issues — use technical-seo-checker. 标题优化/元描述/Schema标记/结构化数据

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-3

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

A well-structured, actionable skill body with clear workflows, validation feedback loops, and sound progressive disclosure. Its main weakness is token efficiency: repeated reference listings and inherited skill-contract boilerplate add tokens that do not earn their place.

Suggestions

Remove the standalone "Reference Materials" section — the same files are already linked inline under each mode's Reference callout, so the duplicate listing is pure overhead.

Trim the inherited contract boilerplate (hot-cache/open-loops promotion, pending-decision rules, handoff-summary shape pointer) to a single concise line, or push it into the shared skill-contract reference rather than repeating it in SKILL.md.

Consolidate the two scope-guard statements (the inline Scope guard block and the Next Best Skill conditional) so the deprecation/chain-complete rules are stated once.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but it carries boilerplate (handoff-summary shape, hot-cache/open-loops/pending-decision promotion rules) and lists the same reference links twice — once inline in Instructions and again in Reference Materials — so it could be tightened.	2 / 3
Actionability	Concrete guidance throughout: character limits (50-60, 150-160), enumerated OG/Twitter tag sets, an executable pre-flight command (`python3 .../schema_lint.py <url>`), and pointer-to-template references; for an instruction-only skill the direction is specific and copy-paste oriented.	3 / 3
Workflow Clarity	Both modes are numbered sequences with explicit validation checkpoints — C01/C02 alignment checks with rewrite feedback loops, schema validation steps, a pre-flight lint, deprecation flags, and "Done when" criteria — matching the level-3 anchor.	3 / 3
Progressive Disclosure	SKILL.md is an overview that signals eight one-level-deep reference files with descriptive links, all of which exist in references/, and content is appropriately split with easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that states concrete outputs, quotes natural trigger phrasings, and explicitly bounds its scope against neighboring skills. The trailing Chinese summary tag is minor redundancy and does not materially weaken any dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Produces title/description options, an OG+Twitter block, and validated JSON-LD for the document head" — matching the level-3 anchor of several specific concrete actions.	3 / 3
Completeness	An explicit "Use when the user asks to..." clause answers when, and the "Produces..." clause answers what, satisfying the level-3 anchor for both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	Natural user phrasings are quoted directly — "optimize meta tags", "write title tags / meta descriptions", "add Open Graph or Twitter cards", "generate schema / JSON-LD" — giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	The scope guard "Not for body copy — use content-writer; not for crawl/index technical issues — use technical-seo-checker" carves a clear niche with distinct triggers unlikely to conflict with sibling skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

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 — 13 / 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
relative_links	Relative link issues: 10 suspicious	Warning

	Total	13 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: seo-geo/implement/serp-markup-builder/SKILL.md
Commit: 4a77c48

Reviewed: 9 days 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.