CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fixing-metadata

Fix metadata issues. Use for SEO/social metadata audits or fixes.

Quality

73%

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 ./.agents/skills/04-develop/01-ui-skills-dot-com/fixing-metadata/SKILL.md
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 well-executed instruction-only skill: terse, specific, rule-driven guidance with a priority system and a real verification gate (pnpm commands plus GO/NO-GO reporting). The main gaps are unquantified thresholds in a few rules, a duplicated tool-boundary constraint, and the absence of a single explicit step-by-step workflow section.

DimensionReasoningScore

Conciseness

The body is a lean checklist that assumes Claude's competence — no explaining what SEO or Open Graph is — with only minor trims available: the framework/library constraint is stated twice ("Do not introduce new frameworks or SEO libraries unless explicitly requested" and "do not migrate frameworks or SEO libraries unless requested") and the "Source: ui-skills.com." line adds no guidance. Not 5 because those redundant tokens exist.

4 / 5

Actionability

Rules are concrete and checkable ("og:url must match the canonical URL", "set twitter:card appropriately, summary_large_image by default") and the Verify section gives executable commands (pnpm lint/test/build/verify) with a defined GO/NO-GO outcome. Not 5 because several directives are unquantified — "keep titles short and readable", "prefer correct image dimensions" with no pixel values, "a sensible og:type".

4 / 5

Workflow Clarity

A coherent review sequence is present: a defined report format (violation snippet + why + fix), explicit prioritization ("fix critical issues first (duplicates, canonical, indexing)"), cross-field consistency checks, and a final validation step with commands and a GO/NO-GO gate. Not 5 because the sequence is distributed across sections rather than presented as one explicit ordered workflow.

4 / 5

Progressive Disclosure

No bundle files exist, and the flat SKILL.md is well organized: a priority table serves as an overview, category sections mirror it, and everything sits at one navigable level. Not 5 because at roughly 115 lines it exceeds the under-50-line simple-skill exception, and no quick-start/summary distills the highest-priority rules.

4 / 5

Total

16

/

20

Passed

Description

58%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 follows the right pattern — third person, terse, with an explicit "Use for..." trigger — and earns full credit for having both what and when. Its weakness is vagueness: only two generic actions and a thin set of trigger keywords, leaving natural terms like "meta tags", "Open Graph", and "favicon" uncovered.

Suggestions

Enumerate 2-3 concrete capabilities instead of the generic "Fix metadata issues", e.g. "Audit and fix page titles, meta descriptions, canonical URLs, robots directives, and Open Graph/Twitter card metadata."

Broaden trigger terms to include natural user phrasings: "Use when the user mentions SEO, meta tags, Open Graph, Twitter cards, favicons, canonical URLs, or share previews."

Lead with the web-page context (e.g. "Fix HTML page metadata") to reduce collision risk with file/EXIF or code-metadata skills.

DimensionReasoningScore

Specificity

"Fix metadata issues" and "audits" name the SEO/social metadata domain with 1-2 concrete actions, but the actions are generic and no specific capabilities (titles, canonical, Open Graph, JSON-LD) are enumerated, matching the '1-2 concrete actions, not comprehensive' anchor. It falls short of 4 because 'several specific actions' with minor gaps are required.

3 / 5

Completeness

It answers both parts: what ("Fix metadata issues") and an explicit when ("Use for SEO/social metadata audits or fixes"), matching the 'has both what and when; when could be more explicit or specific' anchor. Not 5 because the 'what' is vague rather than a comprehensive concrete enumeration.

4 / 5

Trigger Term Quality

"SEO", "social metadata", "audits", and "fixes" are natural user terms, but common variations users actually say — "meta tags", "Open Graph", "Twitter card", "favicon", "title tag" — are missing, which is more than the 'a few natural terms missing' allowed by the 4 anchor.

3 / 5

Distinctiveness Conflict Risk

The "SEO/social" qualifier carves a recognizable niche, but the leading phrase "Fix metadata issues" is generic — 'metadata' also names file/EXIF/code metadata — so it could still overlap with adjacent web-dev or file-metadata skills, matching the 3 anchor. It lacks the format-level specificity of the 4 anchor.

3 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

marchatton/agent-skills

Path

.agents/skills/04-develop/01-ui-skills-dot-com/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.