CtrlK
BlogDocsLog inGet started
Tessl Logo

fixing-metadata

Audit and fix HTML metadata including page titles, meta descriptions, canonical URLs, Open Graph tags, Twitter cards, favicons, JSON-LD structured data, and robots directives. Use when adding SEO metadata, fixing social share previews, reviewing Open Graph tags, setting up canonical URLs, or shipping new pages that need correct meta tags.

83

1.00x
Quality

78%

Does it follow best practices?

Impact

94%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/fixing-metadata/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, concrete ruleset that avoids over-explaining concepts Claude already knows. Its main weaknesses are redundant sections (when-to-apply and review guidance restate other parts) and a workflow whose validation is too narrow for a batch-fixing operation.

Suggestions

Collapse or remove the 'review guidance' and 'when to apply' sections, which restate the Workflow and the description's triggers; keep one canonical location for each.

Add a fix-and-reverify feedback loop and broaden the validation checkpoint beyond social cards — e.g., confirm duplicates are gone, canonical/og:url agree, and JSON-LD passes a validator after fixes.

Name concrete verification tooling (e.g., a JSON-LD/schema validator, a social-card preview tool) so the 'verify on a real URL' step is executable rather than aspirational.

DimensionReasoningScore

Conciseness

The rule bullets are lean and assume Claude's competence (no explaining what OG tags or canonical URLs are), but the 'when to apply' section duplicates the description's triggers and 'review guidance' restates the workflow steps, adding redundant tokens that could be trimmed.

3 / 5

Actionability

Rules are concrete and specific ('og:url must match the canonical URL', 'images must use absolute URLs', 'twitter:card ... summary_large_image by default'), giving mostly actionable guidance; minor gaps are that verification steps name no concrete tool (e.g., no JSON-LD validator or card-preview method).

4 / 5

Workflow Clarity

A clear 5-step sequence exists with one verification checkpoint (step 4, 'verify social cards on a real URL'), but for a batch metadata-fixing operation the validation is partial and lacks a fix-and-reverify feedback loop, capping it at 3.

3 / 5

Progressive Disclosure

Content is well-organized with a priority table, clear section headers, and easy navigation in a single appropriately-scoped file; it earns 4 rather than 5 because there are no external references (none strictly needed) and the file exceeds the ~50-line simple-skill exception for a default 5.

4 / 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.

A strong, well-scoped description that explicitly answers both what and when with concrete, natural trigger phrases and comprehensive metadata coverage. The only minor weakness is a narrow action vocabulary (audit/fix) despite the rich target enumeration.

DimensionReasoningScore

Specificity

Concrete actions 'Audit and fix' are applied to a comprehensive, explicitly enumerated list of metadata types (titles, meta descriptions, canonical URLs, OG tags, Twitter cards, favicons, JSON-LD, robots), but the action vocabulary is narrow (only audit/fix), leaving it just shy of the multiple-distinct-actions bar at 5.

4 / 5

Completeness

It clearly states both what it does ('Audit and fix HTML metadata including...') and when to use it ('Use when adding SEO metadata, fixing social share previews...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when' clause covers natural phrases users actually say — 'SEO metadata', 'social share previews', 'Open Graph tags', 'canonical URLs', 'shipping new pages' — with good synonym coverage and no jargon-only or generic language.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (HTML/SEO metadata) with distinct triggers (SEO metadata, social share previews, OG tags, canonical URLs) and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
ibelick/ui-skills
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.