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.

89

1.00x
Quality

86%

Does it follow best practices?

Impact

94%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%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-organized, actionable reference-style skill body with concrete metadata rules grouped by priority. Its main weakness is redundancy: the workflow, 'when to apply', and 'review guidance' sections overlap, and the workflow lacks an explicit error-recovery loop.

Suggestions

Collapse the redundant 'when to apply' and 'review guidance' sections into the opening workflow to remove duplicated guidance (improves conciseness).

Add an explicit feedback loop to the workflow (e.g., 'if social cards or og:url do not validate against the canonical, fix and re-verify') to raise workflow clarity.

Consider moving the eight detailed rule-category sections into a referenced file (e.g. RULES.md) so SKILL.md reads as a tighter overview, given the body is ~100 lines.

DimensionReasoningScore

Conciseness

The rule lists are lean and avoid explaining concepts Claude already knows, but the 'when to apply' and 'review guidance' sections substantially restate the opening workflow and description triggers, so it could be tightened.

2 / 3

Actionability

Concrete, specific do/don't rules throughout ('og:url must match the canonical URL', 'Open Graph and Twitter images must use absolute URLs', 'set twitter:card... summary_large_image by default'); as an instruction-only skill, absence of code is not penalized.

3 / 3

Workflow Clarity

A numbered 5-step workflow with one validation checkpoint ('Verify social cards render correctly on a real URL, not localhost') exists, but there is no explicit fix-and-retry feedback loop and the workflow overlaps with the redundant 'review guidance' section.

2 / 3

Progressive Disclosure

A single self-contained file with no nested references, organized into a priority table and clearly headed sections; the concise rule format is appropriately kept inline rather than split out.

3 / 3

Total

10

/

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, concise description that names concrete capabilities and gives explicit, natural trigger phrasing in third person. It clearly communicates both what the skill does and when to use it with minimal fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and targets — 'page titles, meta descriptions, canonical URLs, Open Graph tags, Twitter cards, favicons, JSON-LD structured data, and robots directives' — in third person voice, matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what ('Audit and fix HTML metadata including...') and when (an explicit 'Use when...' clause), satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Natural user phrasing is well covered: 'adding SEO metadata, fixing social share previews, reviewing Open Graph tags, setting up canonical URLs, or shipping new pages that need correct meta tags'.

3 / 3

Distinctiveness Conflict Risk

Scoped to HTML/SEO metadata with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.