og-url-match

Use when auditing Open Graph tags or investigating why social share counts appear low. Applies to any page with both canonical-url and og:url tags.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/og-url-match/SKILL.md

Quality

Content

77%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 lean, well-structured overview with excellent progressive disclosure and an unambiguous single-action workflow. The main weakness is redundancy: the Check and Code Review sections, plus the intro and Explain sections, restate the same information, which wastes tokens without adding guidance.

Suggestions

Merge the "Check" and "Code Review" sections, which repeat the same comparison instructions nearly word-for-word.

Trim the intro paragraph, which duplicates the "Explain" section's share-count-splitting explanation.

Add one inline example of a flagged mismatch and its corrected tag pair so the Fix section is copy-paste concrete without leaving the overview.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concepts Claude already knows, but "Check" and "Code Review" repeat the same comparison instruction almost verbatim, and the intro paragraph duplicates the "Explain" section, so it could be meaningfully tightened. It is not anchor 2 because there is no generic padding or unnecessary explanation.	3 / 5
Actionability	Guidance names exact tags and attributes ("<meta property='og:url' content='...'>" vs "<link rel='canonical' href='...'>") and concrete mismatch dimensions (http vs https, www, query strings, trailing slash), which is actionable for an instruction-only skill; minor gaps remain, e.g. no example of how to report a flagged page or a fixed tag inline.	4 / 5
Workflow Clarity	This is a simple, single-task skill (under 50 lines) and the single action — compare og:url with canonical, flag mismatches, set og:url to match — is unambiguous across ordered sections (Quick Reference, Check, Fix). No destructive or batch operations exist, so the validation cap does not apply.	5 / 5
Progressive Disclosure	The body is a concise, well-sectioned overview that appropriately delegates code examples and framework-specific guidance to a clearly signaled, real one-level-deep reference ("see `references/rule.md`"), which exists and contains that detail. Navigation is easy and content is appropriately split.	5 / 5
	Total	17 / 20 Passed

Description

70%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 has strong, explicit trigger guidance and distinctive domain keywords, but it is heavier on 'when' than 'what' — it never states the concrete action of comparing og:url to the canonical tag. Adding one clause describing the comparison-and-flag capability would lift specificity and completeness.

Suggestions

State the core capability explicitly, e.g. "Compares the og:url meta tag against the canonical link tag and flags any mismatch" before the trigger clause.

Add common trigger synonyms such as "og tags", "meta tags", or "Facebook/link preview" to broaden natural-term coverage.

Clarify what the skill does on mismatch (flags pages, recommends the fix) so the 'what' is as concrete as the 'when'.

Dimension	Reasoning	Score
Specificity	"auditing Open Graph tags" and "investigating why social share counts appear low" name the domain with 1-2 concrete actions, but the description never states the core capability (comparing og:url against the canonical tag and flagging mismatches), so coverage is not comprehensive as anchor 4 requires.	3 / 5
Completeness	The explicit "Use when auditing... or investigating..." clause clearly answers 'when', and "auditing Open Graph tags" plus "Applies to any page with both canonical-url and og:url tags" provide a what/scope, but the what stays generic about the actual check performed, so it falls short of anchor 5's concrete what-plus-when pairing.	4 / 5
Trigger Term Quality	"Open Graph tags", "social share counts", "canonical-url", and "og:url" are natural phrases a user would say, but common variations like "og tags", "meta tags", "Facebook/link preview", or "SEO audit" are missing, matching the 'good coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	Triggers like "og:url", "canonical-url", and "social share counts" define a clear niche with minimal conflict risk, though it could overlap with sibling SEO/Open-Graph audit rules in a broader suite, matching the 'mostly distinct' anchor rather than anchor 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/og-url-match/SKILL.md
Commit: 7bfd868

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.