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 or reviewing SEO and social metadata.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/fixing-metadata/SKILL.md

The canonical home for this skill is fixing-metadata in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a well-organized, lean reference of concrete metadata rules with a clear sequenced workflow and a verification checkpoint. Main gaps are a missing fix-retry feedback loop, some redundancy between workflow and review guidance, and no concrete tag/code examples.

Suggestions

Add an explicit feedback loop to the workflow (e.g., "If a real-URL card preview fails, fix the tag and re-verify") to push workflow_clarity toward 5.

Remove the redundant "review guidance" bullets that restate workflow steps, or fold them into the workflow to improve conciseness.

Add one concrete correct-vs-incorrect example (e.g., a sample Next.js metadata export or a minimal OG tag block) to strengthen actionability.

DimensionReasoningScore

Conciseness

The body uses lean bullet lists and avoids explaining concepts Claude already knows, but the "review guidance" section restates workflow steps (fix critical issues first, ensure agreement, verify on a real URL, keep diffs minimal), a minor redundancy that fits anchor 4.

4 / 5

Actionability

Concrete directives like "og:url must match the canonical URL", "Open Graph and Twitter images must use absolute URLs", and "summary_large_image by default" are specific and actionable, though no executable code/tag examples are given; this matches anchor 4 for an instruction-only skill.

4 / 5

Workflow Clarity

The 5-step workflow has a clear sequence and an explicit verify checkpoint ("Verify social cards render correctly on a real URL, not localhost"), but lacks a validate-fix-retry feedback loop; this is anchor 4 (clear sequence, minor validation gaps) since validation is present.

4 / 5

Progressive Disclosure

Content is well-organized into named sections plus a priority table, all inline with no bundle references; at roughly 100 lines it is good structure with minor organization gaps rather than the ideal split of anchor 5.

4 / 5

Total

16

/

20

Passed

Description

78%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 concrete, well-scoped, and explicitly pairs a what with a when clause, with strong distinctiveness. It could improve by adding more distinct action verbs and a few more natural trigger synonyms.

Suggestions

Add more concrete action verbs beyond "audit and fix" (e.g., generate, validate, standardize) to strengthen the specificity dimension.

Include common trigger synonyms like "meta tags", "rich snippets", or "schema markup" to broaden natural keyword coverage.

Tighten the "Use when" clause with more specific concrete triggers (e.g., "Use when adding Open Graph images, fixing duplicate canonical tags, or shipping shareable marketing pages").

DimensionReasoningScore

Specificity

"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" gives comprehensive domain coverage but only two action verbs (audit/fix), so it fits anchor 4 rather than the 5-anchor's multiple distinct verbs.

4 / 5

Completeness

It clearly states what ("Audit and fix HTML metadata including...") and when ("Use when adding or reviewing SEO and social metadata"), but the when clause is somewhat broad rather than a set of concrete trigger phrases, so it sits at anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Natural terms like "page titles", "canonical URLs", "Open Graph", "Twitter cards", "favicons", "SEO", and "social metadata" are present, but common synonyms such as "meta tags", "rich snippets", or "schema markup" are missing, matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

HTML metadata, SEO, and social cards form a clear, narrow niche with distinct triggers and minimal overlap with unrelated skills, matching anchor 5.

5 / 5

Total

17

/

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
administrakt0r/AI-Agents-Safe-Coding-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.