CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a well-structured, highly actionable dual-mode instruction skill: concrete character limits, runnable commands, explicit validation and failure-recovery loops, and a clean one-level reference bundle that fully resolves. Its only weakness is mild token redundancy from double-listing the references and carrying host-framework ceremony. Strong overall; the small conciseness wins are optional.

Suggestions

Drop the consolidated "## Reference Materials" section (or the per-mode Reference blockquotes) — the same eight files are listed twice; citing each file once at its point of use saves ~10 lines.

Trim the host-framework ceremony (Skill Contract reads/writes/promotes details, global-termination rules) to the minimum the host requires, since it competes for context without guiding the markup task itself.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence (no 'what is JSON-LD' padding), and the dated deprecations are properly quarantined in a labeled "Rich-result deprecations" block, but there is trimmable redundancy: the per-mode Reference blockquotes re-list the same eight files again in "## Reference Materials", and Skill Contract / Next Best Skill / global-termination ceremony adds tokens beyond the core task. Not a 3 because the padding is minor and localized, not whole sections of unnecessary explanation.

4 / 5

Actionability

Guidance is fully executable: exact limits ("keep near 50-60 characters", "target 150-160 characters"), a copy-paste pre-flight command `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/schema_lint.py" <url>`, a concrete DOM check `document.querySelectorAll('script[type="application/ld+json"]')`, named validators, and a fill-in Quick Start pattern per mode. Not a 4 because commands and specifics are complete enough to run without improvisation, and examples cover the common meta and schema cases.

5 / 5

Workflow Clarity

Each mode has a numbered sequence with explicit validation and feedback loops — "if C01 fails, rewrite the title; if C02 fails, restructure content or rewrite the description", schema step 3's validation steps and final checklist, "Done when" acceptance criteria per mode, and a recovery path for the JS-injected JSON-LD false negative. Not a 4 because checkpoints, error-recovery loops, and checklists are all explicitly present, not merely implied.

5 / 5

Progressive Disclosure

The SKILL.md stays an overview while all eight bundle files in references/ exist, match their cited content, and are each one hop from SKILL.md with a labeled description of what they contain; the two sibling pointers inside the detail files (e.g. schema-instructions-detail.md → schema-templates.md) are supplementary, since SKILL.md links every file directly. Not a 4 because there is no content reachable only through a chain, and navigation is signposted both inline per mode and in a consolidated list.

5 / 5

Total

19

/

20

Passed

Description

100%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 an exemplar of the form: quoted natural-language triggers, a concrete third-person statement of deliverables, and explicit negative boundaries against neighboring skills. It answers 'what' and 'when' with equal specificity and covers synonyms bilingually. No changes needed.

DimensionReasoningScore

Specificity

"Produces title/description options, an OG+Twitter block, and validated JSON-LD for the document head" lists multiple concrete deliverables (title options, description options, OG+Twitter block, validated JSON-LD) that comprehensively cover the document-head markup domain, in third-person voice. Not a 4 because there is no meaningful coverage gap — the named outputs match everything the trigger phrases ask for.

5 / 5

Completeness

Both halves are explicit: "Use when the user asks to ..." gives concrete trigger phrases and "Produces title/description options, an OG+Twitter block, and validated JSON-LD ..." states exactly what it does — matching the anchor-5 exemplar structure. Not a 4 because the 'when' is as explicit and specific as the 'what', with concrete quoted triggers rather than a general 'use when working with...' clause.

5 / 5

Trigger Term Quality

Triggers are literal quoted user utterances — "optimize meta tags", "write title tags / meta descriptions", "add Open Graph or Twitter cards", "generate schema / JSON-LD" — plus the schema type names (FAQ, HowTo, Article, Product, LocalBusiness) and bilingual synonyms (schema↔JSON-LD, 标题优化/元描述/Schema标记/结构化数据). Not a 4 because synonyms and common variations are covered, not just a few keywords.

5 / 5

Distinctiveness Conflict Risk

A clear head-markup niche with explicit negative boundaries — "Not for body copy — use content-writer; not for crawl/index technical issues — use technical-seo-checker" — routes adjacent requests away. Not a 4 because the disambiguation is explicit rather than implied, leaving minimal overlap risk with neighboring SEO/content skills.

5 / 5

Total

20

/

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

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

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.