CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

86%

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

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.

A disciplined, well-structured checklist skill: dense actionable rules, priority ordering, and clean sectioning with no filler. It falls short of top marks on minor redundancy between the workflow and review-guidance sections, unspecified verification methods, and the absence of any feedback loop for failed checks.

Suggestions

Merge or de-duplicate the 'review guidance' section against the Workflow steps — four of its five bullets already appear verbatim in the workflow above.

Make verification concrete: name how to check social cards (e.g., the Open Graph debugger / Twitter card validator on the real URL) and how to detect duplicate title/description/canonical tags (e.g., grep for repeated tags in the rendered head).

Add a feedback loop after the verification step: what to re-check and in what order when cards fail to render or the tags disagree, so fixes converge instead of ending the workflow at a failed check.

DimensionReasoningScore

Conciseness

The body is lean rule-bullets with no concept-explanation padding, but the 'review guidance' section restates workflow steps 3–5 (agreement check, real-URL verification, minimal diffs), creating trimming opportunities that keep it below the top anchor.

4 / 5

Actionability

Most rules are concrete, checkable directives ('Open Graph and Twitter images must use absolute URLs', 'set twitter:card... summary_large_image by default'), but verification steps name no tool or method and 'escape and sanitize' offers no technique, leaving minor gaps.

4 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced by priority with explicit checkpoints (steps 3–4), but there is no feedback loop describing what to do when verification fails or how to re-check after fixes.

4 / 5

Progressive Disclosure

Sections are well organized (workflow, priority table, eight categorized rule blocks) with everything inline and no buried references, but at ~100 lines with no bundle files, the rule catalog could be split into a reference file to keep SKILL.md a leaner overview.

4 / 5

Total

16

/

20

Passed

Description

92%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 description: third-person voice, concrete and comprehensive capability list, and an explicit 'Use when' clause with natural trigger terms. The only gap is mild keyword breadth — a few common synonyms (e.g., 'meta tags', 'head tags') would round out trigger coverage.

DimensionReasoningScore

Specificity

The description lists two concrete actions ('Audit and fix') spanning seven named artifacts (titles, meta descriptions, canonical URLs, Open Graph tags, Twitter cards, favicons, JSON-LD, robots directives) — comprehensive coverage with no material gaps, matching the 5-anchor pattern.

5 / 5

Completeness

It explicitly answers both what ('Audit and fix HTML metadata including...') and when ('Use when adding or reviewing SEO and social metadata') with a concrete trigger phrase, matching the top anchor.

5 / 5

Trigger Term Quality

Natural user phrases like 'SEO', 'social metadata', 'Open Graph', and 'Twitter cards' are present, but common variations such as 'meta tags', 'head tags', or 'share preview' are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The HTML-metadata/SEO niche is clearly staked out with distinct trigger terms, and nothing in the description would plausibly fire for an unrelated skill.

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.

Validation — 15 / 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

Path

skills/fixing-metadata/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.