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

71%

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

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, appropriately split simple skill with clear workflow and good progressive disclosure. The main weaknesses are the duplicated Check/Code Review sections and instruction-level guidance that lacks an executable method for performing the audit.

Suggestions

Merge the '## Check' and '## Code Review' sections — they repeat the same compare-and-flag guidance — to remove redundancy.

Add an executable snippet or command to actually perform the comparison (e.g., a curl/grep one-liner or a small JS snippet extracting both tags), rather than only describing the comparison.

Optionally surface one concrete fix example inline (a before/after og:url tag pair) so the '## Fix' section is copy-paste ready rather than purely descriptive.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence with no concept padding, but the '## Check' and '## Code Review' sections duplicate the same compare-and-flag instruction, so it could be tightened; not a 3 because of that redundancy.	2 / 3
Actionability	Concrete, specific checklist guidance (compare og:url and canonical href; flag protocol/domain/path/query/www/trailing-slash mismatches; strip UTM/session tokens) but the body gives instruction-level direction with no executable method or snippet to actually extract and compare, leaving the 'how' implicit.	2 / 3
Workflow Clarity	A simple single-task skill with an unambiguous action (verify og:url == canonical) and a clear Check→Fix structure; as a read-only audit, the destructive/batch validation cap does not apply.	3 / 3
Progressive Disclosure	A concise well-sectioned overview that signals a single one-level-deep reference (references/rule.md, verified to exist) for full code examples, framework guidance, and verification tooling — content is appropriately split and easy to navigate.	3 / 3
	Total	10 / 12 Passed

Description

72%

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 a strong explicit trigger and a distinct, well-scoped niche, but it states when to use the skill far more clearly than what the skill actually does. Adding a concrete statement of the check (verify og:url matches the canonical URL) would lift specificity and completeness.

Suggestions

Lead with the concrete action, e.g. 'Verifies that og:url exactly matches the canonical URL', before the 'Use when' trigger clause.

Spell out the verification the skill performs ('flag pages where og:url and canonical differ in protocol, domain, path, or query string') so the 'what' is explicit, not implied.

Use the natural term 'canonical URL' (matching rel='canonical') rather than the hyphenated 'canonical-url'.

Dimension	Reasoning	Score
Specificity	Names the domain and some actions ('auditing Open Graph tags', 'investigating why social share counts appear low') but the verbs are generic and it never states the core check (og:url must match canonical), so it is not comprehensive enough for a 3.	2 / 3
Completeness	The 'when' is explicit and strong ('Use when auditing... or investigating...'), but the 'what' — the specific og:url==canonical verification the skill performs — is only implied, never stated, so it does not clearly answer both.	2 / 3
Trigger Term Quality	Includes the precise natural terms a developer would say — 'Open Graph tags', 'social share counts', 'canonical-url', 'og:url' — giving good coverage of the domain vocabulary.	3 / 3
Distinctiveness Conflict Risk	A narrow, well-defined niche (og:url vs canonical matching for share-count attribution) with distinct specific triggers, making it unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 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: 48405aa

Reviewed: about 8 hours 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.